so i've put in some code for e18 and elm 1.8 to be able to do ~/.config for config and $XDG_CONFIG_HOME. now here comes the rub.
this is borderline grey-area a "api/abi break". in that for elm it means a user with stored config gets reset. for e18 it means their config is reset as their old config fir is no longer used. they could just copy over config files to the new location and/or make symlinks. the question is.. is this really a break? should we do it? for now its a #ifdef. i could roll in a lot more code to try and do migrations/copies for you. for e17 we currently have a situation where i am unsure a user will get upgraded to e18 cleanly at the moment, so we may just put in a bunch of migration code explicitly closer to release. for elm - i dont think the library has any business migrating your config... so what do people think? -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
