* Hamish Moffatt
| An advantage of keeping the old library in oldlibs for a while is that
| local admins may have their own binaries compiled against these
| libraries. Rapid replacements of libraries break local binaries.
Not as long as you bump the package name. There's nothing pulling the
ol
On Mon, May 30, 2005 at 11:41:38PM +0200, Philipp Kern wrote:
> Wouter Verhelst wrote:
> > Uh, no. The old binary package should either be removed completely from
> > the archive (in which case all packages that depend on it are instantly
> > uninstallable), or be moved to a separate source package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wouter Verhelst wrote:
> Uh, no. The old binary package should either be removed completely from
> the archive (in which case all packages that depend on it are instantly
> uninstallable), or be moved to a separate source package in section
> oldlibs.
On Mon, May 30, 2005 at 10:18:03PM +0200, Philipp Kern wrote:
> I got some questions to library packaging. If the ABI of a library
> breaks, the SONAME of it gets updated and thus the binary package's
> name. As soon as the new revision gets uploaded the old binary package
> should get NBS (Not Bui
On Mon, May 30, 2005 at 10:18:03PM +0200, Philipp Kern wrote:
> I got some questions to library packaging. If the ABI of a library
> breaks, the SONAME of it gets updated and thus the binary package's
> name. As soon as the new revision gets uploaded the old binary package
> should get NBS (Not Bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear list readers,
I got some questions to library packaging. If the ABI of a library
breaks, the SONAME of it gets updated and thus the binary package's
name. As soon as the new revision gets uploaded the old binary package
should get NBS (Not Built
6 matches
Mail list logo
