why have the libsasl packages been renamed?

[Henrique de Moraes Holschuh]

On Mon, 23 Apr 2007, dean gaudet wrote:
> i've got some locally compiled packages which Depends: libsasl2 ... yet 
> now when i want to dist-upgrade they're slated to be removed because of 
> the new libsasl2-2 packages which have Replaces: libsasl2 ... and of 

[...]

> this seems rather screwed up.

Your dependencies will work fine in Debian stable, but unstable has moved
beyond the old naming.  If you got this error in a backported package,
whomever did the backporting screwed up.  Otherwise, you do have to update
your local package dependencies to follow the development in unstable if
you are tracking unstable.

> so... why was the name changed?

Because of API and ABI issues, I think.  The new naming allow us to change
APIs, ABIs, and shadow ABIs (ABIs of underlying libraries) and track what
gets screwed by that, instead of breaking things *silently* everywhere.
AFAIK, anyway.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh