On Tue, Jul 23, 2002 at 11:35:42AM -0300, Henrique de Moraes Holschuh wrote: > > Would upstream accept it? > We should push them hard to. Versioned symbols is the only sane way to allow > for linkage of both png3 and any other png lib at the same time in a > app+library stack. > > What would it involve? > Breaking the ABI for libpng3. Again. However, this would be the last time > such ABI changes force a full recompile of the apps AND libraries using > libpng. No, it does NOT require breaking the ABI. A symbol version is additional information, which does not break compatibility with applications that look for the unversioned symbol. libpng3+versioning is still libpng3. (You do have to bump the shlibs dependency information, because new apps won't work with old libs -- but that's routine.) > It really should be done upstream. You could point them to Sleepycat DB and > GNU libc as examples to be followed. They could release libpng4 which is > just libpng3 + versioned symbols, and deprecate libpng3. Support from upstream is better, but it's still a win for us if we implement it in Debian first. And once we've implemented it and shaken the bugs out, it may be easier to get upstream to adopt it. Steve Langasek postmodern programmer
Attachment:
pgpzzFz7sWQyx.pgp
Description: PGP signature