Re: one binary package created by different source packages, will the old source package disappear?
On Mon, Mar 20, 2006 at 12:03:13PM +0100, Frank Küster wrote:
> Hi,
>
> assume the following scenario:
>
> - Source package foo creates binary packages libfoo1 and libfoo-dev
> - source package foo2 creates binary packages libfoo2 and libfoo2-dev
>
> Since both versions are API-compatible, libfoo2-dev is renamed to
> foo-dev, replacing the old binary package from source package foo. Will
> the complete source package foo have to disappear, or will foo and the
> binary package libfoo1 continue to be available?
If foo2 didn't exist yet, you'd most likely want to start your
transition by having a new 'foo' instead, creating libfoo2 and
libfoo-dev. (ABI/SONAME change, but no API change, so -dev remains named
the same). Transition can be done mostly/totally via binnmu's, and
libfoo1 will be semi-automatically dropped.
If foo2 already exists, I'd still go for that solution, but you'll then
need to ask for foo2 removal via a bug to ftp.debian.org.
Because there is API compatibility, I'm assuming here it makes not much
sense to keep both libraries in at the same time. If you want to keep
libfoo1 available (would need a somewhat decent reason, ideally), you'll
need separate source package names (indeed foo2 then), and will need to
make a new upload of 'foo' stopping to provide a -dev package.
Otherwise, ít'll be impossible to do security uploads without making
those changes at that time -- however, libfoo1 will remain available,
even lacking such upload.
N.B.: Such questions are easier to answer (less guessing needed w.r.t.
missing information) given a real example.
--Jeroen
--
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
Reply to: