From owner-freebsd-hackers Sun Nov 30 16:22:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA16531 for hackers-outgoing; Sun, 30 Nov 1997 16:22:02 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16513 for ; Sun, 30 Nov 1997 16:21:52 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id TAA00960; Sun, 30 Nov 1997 19:19:57 -0500 (EST) X-Authentication-Warning: picnic.mat.net: chuckr owned process doing -bs Date: Sun, 30 Nov 1997 19:19:56 -0500 (EST) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "John S. Dyson" cc: reyesf@super.zippo.com, hackers@freebsd.org Subject: Re: How is selection made of what goes into CDrom? In-Reply-To: <199711302324.SAA02089@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 30 Nov 1997, John S. Dyson wrote: > Chuck Robey said: > > On Sun, 30 Nov 1997, Francisco Reyes wrote: > > > > > I was wondering how is the selection made of what goes into the > > > CDrom? > > > Is the CVS repository used by most users or just a few? > > > > > > Personally I find that it would have been more useful to have the > > > sources for all the programs somewhere (ie a second live file system > > > CD) in an untar format. Alternatively a list of where the sources are > > > in the first CD and a small script to get a program out would be just > > > as good. For example recently I wanted to look at the source code for > > > "renice". Getting the entire usr.bin took too much space. > > > > > > > You know that the source for renice (and all the other parts of FreeBSD) > > are inside that CVS archive? cvs is really complicated to learn, but > > pretty well worth it. > > > > For the average CVS user (commits/checkouts/adds) like me, CVS is plainly > simple to use. It appears that sometimes it is necessary to do some fancy > dancing though, but just to retrieve various versions of the code, CVS > usage is trivial (as it should be.) > John, compare the cvs flags with the flags for something more common user-ish, like maybe ls. I don't know, is there _any_ other program so broken that it uses multiple sets of flags, whose context changes with subcommands? I know how to use it, but the complication, and difficulty in getting a running start, coupled with the extreme embarrassment of what happens if a mistake is committed, kept _me_ from using one for a while. Winter project for me (note to personal whiteboard): write a simple cvs user manual. Maybe not complete, but enough to get things going for the average user! > > -- > John > dyson@freebsd.org > jdyson@nc.com > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------