https://bugs.gpodder.org/show_bug.cgi?id=68
--- Comment #15 from Thomas Perl <[email protected]> 2009-07-23 21:43:16 GMT --- (In reply to comment #14) > Maybe, but this way I don't have to lauch gtkpod very often. And if the > extended database is not updated, gtkpod freaks out and it very long to way > for > him to correct everything. And with my previous ipod, when it happened, it > fliped itseft into read-only mode and I had to disconnect and reconnect it > before saving the database with gtkpod. The "gtkpod extended database" is really only used by gtkpod, so you will need an up-to-date database only when using gtkpod (and that is when you are launching gtkpod). > Perhaps with my new one it would be ok. And maybe what gtkpod is doing is > exactly what gpodder does when it deals with the extended database. It's exactly the same (basically calculating checksums of the files on the iPod and writing it to the textfile iTunesDB.ext). The difference is that gtkpod always knows how to do it, because it's the single application that uses this data AFAIK. Which means that by doing it all inside gtkpod it's possible to allow gtkpod to change or extend the format of the iTunesDB.ext file without having to change gPodder. > Anyway, I'll stick with the version I have to be sure to have the extended > database feature. I'd be very thankful if you could try to use the latest version possible, because bugfixes and feature improvements are done there. Of course, this time, it's a feature regression for you, but it's "cleaner" this way. And, you can always simply apply the reverse patch of the commit that removed the gtkpod extended database writing (that is, use "patch -R"). Thanks for your feedback and your understanding :) -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
