On Fri, 17 Apr 2009 12:27:34 +0400 sda <dmitry.serpok...@gmail.com> said:
> please look above and let's find some sane solution. API/ABI change > should in theory change SONAME (i.e. libfoo.so.0.1 -> libfoo.so.0.2) > but ... we're in a real world and we're working with svn. why not to use > changes of Version along with the proposed above schema on Version > naming? because the only way to break abi with version is to go libX.so.1.x.x -> libX.so.2.x.x ie increase MAJOR number. i do NOT ant to change the version of the lib as when evas/ejde/whatever get released i want them to be: libevas.so.1.0.0 and AFTEr 1.0.0 relase we will use so version for api breaks - and the evas RELEASE will also show it. the source release version, package version ANd lib so version will/should MATCH! i want them to MATCH! i want it to all be simple and consistent so it's easy to know whats intstalled, and what will or wont work with it. until 1.0.0 happens there is NO WAY to break an abi WITHOUT changing soname i.e. libX-pre01.so.x.x.x -> libX-pre02.so.x.x.x etc. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
