On Wed, Apr 24, 2013 at 03:11:53PM -0700, Russ Allbery wrote: > >> We have a plenty of libraries (and other packages) who do conflict > >> between themselves, so we know the drill. > >> > >> Also Debian no longer ships libjpeg62, so there's not conflict there > >> at least for baseline implementation (libjpeg62 API/ABI). Remember we > >> are speaking about wheezy+1 now. > >> > >> For libjpeg8-turbo you can just declare Conflict with libjpeg8 and it > >> will be used just in the applications who explicitly link with > >> libjpeg-turbo-dev. > > > Which means that some applications won't be coinstallable? > > For this to be viable, you'd need to do the same thing that we do for MIT > Kerberos and Heimdal, namely: > > * Create conflicting -dev packages. > - For special bonus points, have both conflicting and co-installable > ones, as with the -multidev Kerberos packages. > * Give the libraries different SONAMEs. > * Ensure both libraries use symbol versioning with different versions. > * Ensure the shared library packages are coinstallable. This will also lead to an unnecessary choice for each maintainer of packages using libjpeg: they will need to choose the implementation to use. -- WBR, wRAR
Attachment:
signature.asc
Description: Digital signature