On Tue, Apr 24, 2007 at 08:48:03AM -0700, Steve Langasek wrote: > On Tue, Apr 24, 2007 at 02:09:42PM +0200, Domenico Andreoli wrote: > > > he already expressed the intention to keep it, curl 7.16.x is on the > > road since oct 2006. > > Grmbl. > > I wonder if it's worth adding a compat shim for the old symbol versions.
uh? > > > Anyway, even if the soname changes, you seem to have changed the names of > > > the -dev packages as well -- if the only incompatible change is dropping a > > > handful of deprecated ftp options, that's *definitely* not warranted. > > > Please revert the -dev package names before uploading to unstable, I'd > > > really rather we didn't have to do sourceful uploads of 120 > > > reverse-dependencies on top of everything else, on account of an upstream > > > decision to turn a non-ABI-breaking change into an ABI-breaking one. > > > the -dev package names went from libcurl3-* to libcurl4-*. how i can > > keep the old ones? should i push the original scheme of some years ago > > in which no soname is in the -dev packages? > > That would be fine with me (and preferable in the general case), so long as > packages that build-depend on libcurl3-dev can still be built -- either by > restoring the libcurl3-dev real package, or by making whatever the new -dev > package is Provides: libcurl3-dev. so it would be: libcurl4-dev provide: libcurl-dev libcurl4-openssl-dev provide: libcurl-dev, libcurl-ssl-dev, libcurl3-openssl-dev libcurl4-gnutls-dev provide: libcurl-dev, libcurl-ssl-dev, libcurl3-gnutls-dev libcurl-dev and libcurl-ssl-dev are already in place since the non-ssl/ssl scission, long time ago. my intention is to add also a non-ssl libcurl flavour with libcurl4-dev. libcurl3-dev has been a transition package to install libcurl3-openssl-dev. hence those depending on libcurl3-dev instead of libcurl3-openssl would have a bug. regards domenico -----[ Domenico Andreoli, aka cavok --[ http://www.dandreoli.com/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
