On Mon, Apr 16, 2007 at 12:33:07PM +0100, Neil Williams wrote: > It's not arbitrary - the SONAME change has already broken compatibility > within Debian. > > There is only on -dev package for either libarchive1 or the useless > libarchive2 so rebuilding is not affected, as soon as libarchive-dev is > updated, builds will use the library provided by the -dev. > > Packages build depend on libarchive-dev, Debian doesn't accept arbitrary > binaries linked to libarchive2, we build from source via libarchive-dev.
Why would Debian not accept binaries linked to libarchive2? I don't see how this is any worse than any other library transition. The original problem that was reported for this bug -- that both libarchive1 and libarchive2 provide the same manpage -- can be trivially fixed without mucking about with all of this. > > It can > > only hurt binary compatibility. > > Vorlon's suggestion of a symlink prevents that. I'm not so sure. Wouldn't binaries built on Debian want a library v1, which wouldn't work on systems that provide v2? Sure, we could run binaries that others build, but they couldn't run binaries that Debian users build. > If the libarchive2 package had been installable alongside the > libarchive1 package, this would have not been a problem but it would > still have been the wrong thing to do, IMHO. libarchive 2.0.25 could > possibly have made it into Etch if GNU libtool conventions had been > followed in the SONAME. Well, again, it doesn't seem impossible to fix the tar manpage problem. Even failing that, if everything that uses libarchive is simply rebuilt sometime between now and the release of lenny, and libarchive2 conflicts and replaces libarchive1... where is the problem? The upgrade and builds should all work fine. > What is your proposed fix for this blocking bug? It seems that the sensible thing is to make libarchive2 conflict and replace libarchive1, and to have anything that was still built against libarchive1 be rebuilt before lenny is released. That looks like approximately 4 packages. -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
