On Sun, 10 Dec 2000, Jason R Thorpe wrote:

:  > Known response.  I don't see the reason for it to be in basesrc based on
:  > this statement.  `Just use pkg_add on a binary....' CVS just isn't the kind
:  > of moving target that, say, NetBSD-current sources are, so all it really
:  > does is add yet more time to a build.
:
: BZZT.  You can't pkg_add the binary if there isn't a binary package
: available.  There are often times where this is the case.

(Please refrain from the "BZZT." and similar rudeness.  I'm trying to have a
discussion here, and this obviously wasn't discussed before it was
imported.)

This is a _very_ simple problem to fix:  build cvs alongside *releases* as a
release binary requirement.

Are there any other operability reasons?  I don't see how having CVS build
with every toplevel build of basesrc does more than add build time.

: If we're going to remote ANYTHING from basesrc, it probably ought to be
: RCS -- CVS no longer requires it, and most people use CVS for version
: controlling these days.

I agree on RCS as well, and have proposed it before, meeting the response of
"well, we don't have a pkgized base system, so buzz off."  However,
technical arguments like these certainly weigh better.

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  http://www.wasabisystems.com/
-- Speed, stability, security, and support.  Wasabi NetBSD:  Run with it.