Scripsit Frank Küster <[EMAIL PROTECTED]>
> - 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,
It absolutely _should_, or be reuploaded with new control and rules
files to create only libfoo1. Otherwise an attempt to recompile
source package foo (say, for a security fix) risks replacing the new
libfoo-dev with an older one.
Probably a better solution would be to rename libfoo-dev to
libfoo1-dev such that if packages that link to libfoo1 reach stable
there will still be a way to rebuild them for security updates without
adding the new-bug risks of switching to a new implementation of the
library.
--
Henning Makholm "It's kind of scary. Win a revolution and
a bunch of lawyers pop out of the woodwork."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
