Subject: Re: Doubled dependancies?
To: Todd Vierling <firstname.lastname@example.org>
From: Johnny C. Lam <jlam@NetBSD.org>
Date: 10/05/2004 15:32:12
On Mon, Oct 04, 2004 at 10:53:10PM -0400, Todd Vierling wrote:
> On Mon, 4 Oct 2004, Richard Rauch wrote:
> > jpeg>=6b
> > jpeg>=6bnb2
> > libungif>=126.96.36.199
> > libungif>=4.1.3nb1
> > png>=1.2.4
> > png>=1.2.6nb1
> > tiff>=3.6.1
> > tiff>=3.6.1nb3
> > ...looks fishy.
> It's normal when you have buildlink3 with multiple different notions of the
> least possible package versions. The build and install chooses a dependency
> that satisfies all the given version constraints. For example, above,
> "png-1.2.4" is not good enough of a dependency for the package as a whole;
> you need at least "png-1.2.6nb1".
> > Shouldn't only the "highest" dependancy be displayed?
> Currently pkgsrc doesn't have the ability to filter it to only the "highest"
> dependency, so it simply records all constraints.
I've moved the code to filter out redundant dependencies from the
buildlink3 area into bsd.pkg.mk, so pkgsrc now supports this for all
Ask and ye shall receive!
-- Johnny Lam <jlam@NetBSD.org>