Subject: Re: pkgsrc documentation, digest and undefined reference to `RMD160Init'
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 03/23/2001 22:20:03
On Fri, 23 Mar 2001, Jeremy C. Reed wrote:
> On Sun, 11 Mar 2001, Matthias Scheler wrote:
> > In article <Pine.LNX.firstname.lastname@example.org>,
> > "Jeremy C. Reed" <email@example.com> writes:
> > > As far as I know, there is not a current (development) tree and a stable
> > > tree for pkgsrc.
> > There is stable one: the snapshot that was distributed with NetBSD 1.5.
What I understand that to mean, in the context of the recent breakage,
is that you can always roll back.
> > > (Can we have a development/testing tree for pkgsrc?)
> > We have. Remember "pkgsrc" is part of NetBSD-current.
> Can you please explain this further?
> Is the up-to-date pkgsrc tree really for only NetBSD current?
Not at all. There is only one pkgsrc, which much work on all the
active branches of the base system. Consider, 1.4.3 and 1.5 came out
at about the same time, and the pkgsrc tar balls included with each
are in fact identical. As a matter of fact, quirks for 1.3.x (the
bzip2 package) have never been categorically removed.
> This is confusing. Consider the following postings; basically they are
> talking about a new pkgsrc used with older versions of NetBSD.
There's no question that pkgsrc has to support older NetBSD systems.
The recent break affected current and 1.4.x alike. I'm actually
pleased with all the attention it got. It means that people are using
pkgsrc -- new users every day -- and they have high expectations.
Branching releases in the base system is painful, but necessary. We've
managed to avoid that so far, in pkgsrc (and xsrc), with only minor breaks.