On Thu, 05 Nov 2015 08:31:08 -0500 Ross Vandegrift <[email protected]> said:
> On November 4, 2015 7:48:53 PM EST, Carsten Haitzler > <[email protected]> wrote: > >On Wed, 04 Nov 2015 11:54:43 -0500 Ross Vandegrift <[email protected]> > >said: > > > >> Hi all, > >> > >> Is there an official stance on sonames in EFL & friends? I see some > >> discussion about this in the archives circa 2009, but it looks like > >> plans changed. See the thread starting at [1]. > >> > >> I'd like to get the Debian packages updated, and I'm just trying to > >> figure out what to expect on this front. > > > >our stance is - you DONT CHANGE OUR SONAMES OR SO MAJOR VERSIONS. do > >not > >change. leave. don't patch. > > > >we did this pre 1.0 because we broke api/abi "at will" pre 1.0. > > > >you also don't change our pkgconfig pc file names or the names of > >header > >files, nor the names of dirs underneath PREFIX/xxx where xxx is bin, > >lib, > >include, share, etc ... :) i.e. > > > >we have things installed in libdir/evas where libdir may > >be /usr/lob, /usr/lib64, /usr/local/lib, /opt/whatever/lib or maybe > >even /usr/lib/i386-linux ... that we allow. all of these dirs MUSt > >share a > >prefix. ie > > > >/usr or /usr/local or /opt/blah etc. - don't move stuff OUT of prefix > >EXCEPT > >etc. that's allowed. :) > > > >does this help? > > Err, not really - I was wondering about when you guys would change a > soname. Sorry for being unclear. we will not change soname. we will actually only change major version number (which is effectively like a soname change) and even then we will do this in a careful way to "move forward" in future. > Looking over the history, I'd guess the plan is to leave them alone. > But maybe an EFL 2.x would trigger a change? I'm not 100% confidant of > that assessment. Just trying to figure out what to expect. actually just a major version change - which is an "abi break" anyway. no need to change soname. what is likely is we will keep out names and at some point go libevas.so.1 -> libevas.so.2 (and same oft other libs), BUT this change will end up a compat api wrapper around some NEW library names likb libefl.so, libeflui.so, libeflcore.so or whatever and we'll use library linking as dependencies to have the old names link in the new libs that they wrap for compat -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
