Subject: Re: When DEPENDS can be upgraded in place
To: Frederick Bruckman <firstname.lastname@example.org>
From: David Brownlee <email@example.com>
Date: 09/08/2000 13:17:34
On Wed, 6 Sep 2000, Frederick Bruckman wrote:
> On Wed, 6 Sep 2000, Hubert Feyrer wrote:
> > OK, and what do you suggest then? Tell them that a lib of <newer version>
> > would be required, judging from information encoded in the (new) "app"
> > pkg?
> Yes, and also update the DEPENDS in the app pkgsrc (if it isn't fixed
> already), and delete the app binary package with the broken dependency
> from the server. [We shouldn't say "app" depends on lib>=1.1 unless
> "app" built against lib-1.2 is known to work with lib-1.1. I don't
> want to lay a heavy "burden of proof" on the pkgsrc maintainer though,
> I just want a way to fix it when someone reports a problem.]
We have two dependencies - the existing build dependencies, and
the 'binary' set.
eg: build may be lib>=1.1, and if you build against 1.1 then
then binary dependencies are lib>=1.1. But if you build against
1.2 then binary dependencies should be lib>=1.2
-- www.netbsd.org: A pmap for every occasion --