[mythtv] [mythtv-commits] Ticket #4560: convert maps.xml (from scripts) into a new DB table / provide ability to add additional maps
Michael T. Dean
mtdean at thirdcontact.com
Thu Jan 31 17:16:39 UTC 2008
On 01/31/2008 11:08 AM, MythTV wrote:
> #4560: convert maps.xml (from scripts) into a new DB table / provide ability to
> add additional maps
> I found that the new mythweather trunk is working great! When I was
> setting up to use the maps (static and animated) from the scripts
> directory, I noticed that there is not currently a way to add additonal
> maps short of manually editing the maps.xml file.
> Would it be possible to move the maps.xml data into the DB in a new table
> as well as providing a way to add new maps to the DB? For example, I live
> in the Dallas, TX USA area and although I can find maps that cover this
> area, none provide detail for Dallas. I added my own entry to the maps.xml
> file to get a local radar image which works great. The draw back is that
> the maps.xml file is overwritten with each svn update.
If you're truly using svn update (as opposed to svn checkout--and you
should not be using svn checkout every time), svn should be merging the
upstream changes into your locally-modified maps.xml.
If you keep a clean checkout in a tarball then update and re-tar the
updated checkout or something, just make a patch with your changes (svn
diff path/to/maps.xml > mythweather_maps.patch) and it will likely apply
without modifications for a /very/ long time (even if maps.xml changes,
it should apply cleanly with offsets--basically, only when the part you
changed is changed upstream will you have to manually merge and
re-generate the patch). I do the tarball-based approach and have a list
of about 10-20 patches that I apply each time I build, and a list of
commands to issue in my build notes (so it's as simple as copy/paste'ing
the patch command).
Of course, you could also make and submit the patch to move the data to
the DB. :)
More information about the mythtv-dev