Subject: Re: CVS commit: pkgsrc/mk/buildlink3
To: Quentin Garnier <firstname.lastname@example.org>
From: Johnny C. Lam <email@example.com>
Date: 01/25/2004 14:15:37
On Sun, Jan 25, 2004 at 08:16:40PM +0100, Quentin Garnier wrote:
> Correct me if I'm wrong, but it's not about binary packages here. What
> the change allows is to keep track of the most restrictive condition for a
> With the ?= assignment, package A could assign BL_DEPENDS.xxx xxx>=2, and
> then package B (in the order of bl.mk inclusion) assign BL_DEPENDS.xxx
> xxx>=1 (because it only depends on a tiny subset of the API that hasn't
> change between 1 and 2 for package xxx). Then, the system would not
> rebuild xxx if xxx-1 is installed, although A needs xxx-2.
> With the += assignement, all conditions are kept, and then you can still
> have the most restrictive in the list, and use that one.
Yes, this is exactly what I'm thinking.
> When buildling a package, you can't depend on several versions of a
> dependency, since there is still only one provided by the pkgsrc tree.
> Of course, bl3 has to make sure only one condition is recorded in the
> binary package, but this is another issue.
I am actively working on this, and will have something working soon.
-- Johnny Lam <firstname.lastname@example.org>