--eVzOFob/8UvintSX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 21, 2002 at 07:18:13PM +0100, ivan.dolezal@vsb.cz wrote:
> Is that the spirit of NetBSD that for day-to-day operation you should not=
 need
> to play with -current tree? <http://www.netbsd.org/Releases/>

How does this in any way involve the current/release division?

pkgsrc functions properly on any version of NetBSD; in all cases it
should be cvs updated. It's not even in the same module as the
NetBSD source. The distinction between -current and -release is that
the former is what you get when you checkout the src module and the
latter is what you get when you checkout the src module with
-rnetbsd-1-6 (or similar, for earlier releases) set. Neither of
these actions will get you pkgsrc; it is wholly separate.

It is quite possible that various ports binary packages are out of
date. TNF is not a commercial operation, as RedHat, Caldera, and so
forth are. Keeping all pacakges for all ports up to date would
require a significant amount of compile time on computers whose use
would have to be donated freely. Would you care to help with some of
that load? Linux distributions are able to keep up with stuff like
this as they need packages for only one (or, in a couple cases, three)
processor architectures.

--=20
gabriel rosenkoetter
gr@eclipsed.net

--eVzOFob/8UvintSX
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (NetBSD)

iD8DBQE9F0n99ehacAz5CRoRAtGDAJ9OFPT3HaWvZAVzYu++OuU4epEviACdEE22
lAPcnjjYCrufm3MbqRWQsJs=
=qahL
-----END PGP SIGNATURE-----

--eVzOFob/8UvintSX--