Date: Tue, 22 Jun 1999 10:32:22 -0700 From: Jamie Norwood <mistwolf@ethereal.net> To: freebsd-questions@freebsd.org Subject: /usr/share/examples/cvsup Message-ID: <19990622103203.A13663@ethereal.net>
next in thread | raw e-mail | index | archive | help
I am wondering if there is some way we could change the naming of files in /usr/share/examples/cvsup. As it is now, we have: README ports-supfile stable-supfile cvs-supfile secure-cvs-supfile standard-supfile doc-supfile secure-stable-supfile www-supfile gnats-supfile secure-supfile Now, many of these are ok. But, specifically, I find the naming of the 'standard' line to be dangerous. I feel these files should be more self- explanatory in naming. Basically, here at work, one of the guys installed a new install of FreeBSD. After spending days configuring it and such, he decided to do a source update. He cd'd to the dir, and ran 'cvsup -g -L 3 -h cvsup3.freebsd.org standard-supfile', assuming it would take him to the most recent version of 3.2-RELEASE. He couldn't have been more wrong... See, 'standard' upgrades you to 4.0-CURRENT. Not something we want running on a prodyuction machine. I feel we would be better off having files more intuitively named, such as: release-supfile current-supfile stable-supfile And secure versions of each. That way newbies who don't realise that standard is anything but will be using the right files. Comments? Jamie -- -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+:+ a--(?) C++++ UB++++ P+ L--(++) E-- W++(--) N++ O? K w(---) O?>+ M?>+ V PS+ PE+ Y+ PGP->++ t+(*) 5+++ X++ R++ tv+ b+ DI++++ D++ G e>+ h--- r+++ y+++** ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990622103203.A13663>