+1 It's been stated on the list recently that this won't be part of the next release, but yes... this definitely needs to happen, it makes it awkward to share presets (which I would consider more "configuration" than "data") between darktable installations that don't share any other part of the "library". Keeping them separate would make keeping incremental backups easier, too.
On 2013-12-01 [email protected] wrote: > While sorting out my library and removing some duplicate photos I > discovered that removing library.db loses module presets too. > > Could I ask what else is stored in there other than library info? > > Could I also make a suggestion that presets are stored elsewehere? It > doesn't seem logical to me to put anything in the db other than > library info. > > Opinions? > > -D > > > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk > _______________________________________________ > Darktable-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/darktable-users ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
