Why new package name libsasl2-2

Andreas Metzler ametzler at downhill.at.eu.org
Wed Oct 18 17:05:24 UTC 2006


On 2006-10-18 Fabian Fagerholm <fabbe at paniq.net> wrote:
> On Tue, 2006-10-17 at 20:11 +0200, Andreas Metzler wrote:
[...] 
> > Once you drop the requirement for having two packages containing
> > /usr/lib/libsasl2.so.2 in the achive everything is easy:
> > 
> > Package: libsasl2
> > Source: cyrus-sasl-2.1
> > Depends: libsasl2-2 (= ${binary:Version})
> > Architecture: any

> Ok, let me see if I understood correctly by explaning this in my own
> words:
[snip, everything correct up to here]
>       * All packages which build against the old package will pull in
>         the new package and the build will work.
[...]

If there is a similar libsasl2-dev dummy package, too. (already there
in SVN ;-)

Ah, BTW these dummy packages should be section oldlibs.

>       * Over time, packages will switch to depend directly on the new
>         package, and when all packages have switched, we can drop the
>         dummy package.

You might choose to keep the dummy packages around for a full release
to ease stable --> stble upgrades, but this is probably not necessary
as library are not installed manually,m but pulled in by dependencies.

> Is this correct? Does it cover the transition completely, or did I leave
> something out?
[...]

I currently cannot see anything else.
cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde



More information about the Pkg-cyrus-sasl2-debian-devel mailing list