On Mon, Aug 5, 2013 at 12:15 PM, Alexis Ballier <aball...@gentoo.org> wrote: > On Mon, 5 Aug 2013 18:10:46 +0200 > Michał Górny <mgo...@gentoo.org> wrote: >> We can simply have multiple virtual versions, each depending >> on the proper jpeg & jpeg-turbo versions. > > you can do it that way, yes. > > what will you do when jpeg 10 is out or when libjpeg-turbo changes its > abi ? wait for each provider to have a release that changes the abi ? > this doesnt sound sane
I think a thorough solution needs to handle the passthrough situation, and ideally the multiple libs per package situation. Our whole versioning system wasn't really set up with this stuff in mind either. We're dealing with ABI/SONAME versions here - not functionality versions. A package with jpeg-turbo SONAME 0.6 might be a superset of all the functionality in SONAME 0.9 - the larger number doesn't mean better, just different. It might still be possible to handle this with subslots as they are currently implemented, but I'd have to really mess around with it to be sure. The logic of higher-number = more-desirable is likely to cause problems - you don't want your system to force you to move from jpeg-turbo to jpeg because only the latter is a dep of a newer virtual. Rich
