Subject: Re: pkgsrc documentation, digest and undefined reference to `RMD160Init'
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Alistair Crooks <email@example.com>
Date: 03/26/2001 13:19:35
On Fri, Mar 23, 2001 at 05:45:29PM -0800, 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.
> > > (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?
> This is confusing. Consider the following postings; basically they are
> talking about a new pkgsrc used with older versions of NetBSD.
> On Fri, 23 Mar 2001, Alistair Crooks wrote about "Re: muhah":
> > pkgsrc runs on Solaris and Linux as well as NetBSD. For anyone who is
> > worried, I, personally, have no intention of making pkgsrc work on
> > Windows. Openssl is only in later versions of the base system on
> > NetBSD. For previous versions, there is only the package, and there
> > we run into bootstrap problems again.
> On Fri, 23 Mar 2001, Greywolf wrote about "Re: muhah":
> > What you are failing to understand is that if one upgrades to a current
> > pkgsrc while choosing not to upgrade userland/kernel beyond 1.4(.x),
> > because we're now using SHA1 checksums instead of MD5, since those versions
> > of the OS do not have OpenSSL, digest is a much better choice.
> In addition, why doesn't
> http://www.netbsd.org/Documentation/software/packages.html indicate that
> the current pkgsrc is only for -current userland and kernel.
I know of people using "current" pkgsrc on NetBSD 1.3.3.
I see no reason why we shouldn't continue to support them.