Subject: Re: When DEPENDS can be upgraded in place
To: NetBSD Packages Technical Discussion List <tech-pkg@NetBSD.ORG>
From: Frederick Bruckman <>
List: tech-pkg
Date: 09/08/2000 13:09:36
On Fri, 8 Sep 2000, Greg A. Woods wrote:

> [ On Friday, September 8, 2000 at 10:41:58 (-0500), Frederick Bruckman wrote: ]
> > Even under a.out, the new binary would only continue to use
> >, if the binary was running when you upgraded. The next
> > time you invoke it will load
> Yup.
> > Why do you even want old
> > libraries hanging around?
> because you will have bumped the major version....

You're not seriously suggesting that we modify every package to bump
it's major version number, every time the author bumps the minor????  
I don't where to begin, to tell you what's wrong with that plan. This
tops your previous suggestion, to abolish shared binaries altogether.

Please keep the goal of the discussion in mind. We want the package
system to accomodate upgrading shared libraries without upgrading the
binaries that depend on them, in the _same_ way that you can do that
WITHOUT A PACKAGE SYSTEM. When I update NetBSD base, or xsrc, I
install shared libraries on top of other shared libraries, sometimes
with minor version bumps, and all my previously installed binaries
just work. Keeping the old library around, or worse, forcing the
binary to use the old library, trivially satisfies the requirement,
but fails to address it's purpose.