Subject: Re: pkg dependencies bite
To: Masao Uebayashi <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 02/04/2001 22:31:07
On Mon, 5 Feb 2001, Masao Uebayashi wrote:
> > > > - if a package has any dependency, make it depend against a package
> > > > which is the lowest version in compatible packages
> > Or how about build a baseline against the tag, then only update
> > packages as a group whose version numbers differ from the baseline
> > versions (so as not to overwrite the baseline packages). I'm working
> > on a set of scripts to help do this. I have most of the engine done --
> > a script to pluck the dependencies from pkgsrc, and another (a
> > four-pass awk script) to massage them into groups, but I'm still
> > struggling with how the command line options should look.
> Sounds nice, but how do you know a "baseline" of a package? I guess
> that we may have to make packages have stricter version so that we can
> pose dependencies on them and avoid dependency-related troubles.
I mean a "baseline" for the whole collection. The concept has no
meaning for a single package. It means to me a complete set of all
packages built against the same release tag.