Hi, On Mon, Jun 21, 2010 at 09:44:56PM +1000, Michael Lamothe wrote: > > programs), it should be possible to export a channels.conf . Without that, > > you > > have to create channels.conf with other tools > > Not true, > > 1. sqlite3 ~/.local/share/me-tv/me-tv.db ".dump channel" > channel.sql > 2. sqlite3 ~/.local/share/me-tv/me-tv.db < channel.sql > > 1. will export channels, 2. will import channels. Of course, you can > always just copy the database file.
you can certainly handle this as a documentation bug, i.e. document ~/.local/share/me-tv/me-tv.db in the FILES section of the man page, including the database schema and the fact that overwriting one of the tables doesn't destroy the integrity of other data in the database as would be the case with most database applications. Having 1. and 2. as examples would do no harm also. Just adding a menu item and an fprintf() in a loop seems easier, though. Data migration should work both ways, if you added the ability to import data in a common file format understood by other programs, you seem to accept that it may be useful to import the other programs' settings into your program. Then you should also consider the fact that the same people that did this may want to migrate their (modified) settings even further, instead of having their data locked into your program. This is easiest done by exporting said common file format. -- 00000000 72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a r...@strcmp.de. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
