[ On Sunday, March 3, 2002 at 17:14:29 (-0500), richards@CS.Princeton.EDU wrote: ]
> Subject: misc/15797: Lack of CVSROOT/options file foils CVSup $NetBSD$ expansion
>
> 
> 	CVSup, by default, does not expand the $NetBSD$ keyword.  Hence
> 	files tracked by CVSup have off-by-one revisions in $NetBSD$.
> 
> 	(I know that NetBSD is reluctant to imply that CVSup is supported,
> 	but this is a small, quick fix that benefits many people.)

I didn't know CVSup used a different configuration file from CVS....

NetBSD's CVS of course has a similar feature, and for CVS it is enabled
in the CVSROOT/config file.  The content necessary to set a local tag is
similar to what you show for CVSup:

	tag=NetBSD

Would CVSup need the "options" file if CVSROOT/config existed and
contained at least the above line?

In any case there should be a CVSROOT/config file shipped with the
NetBSD CVS repository for similar reasons that you cite for CVSup's
CVSROOT/options (files in locally checked out working directories have
off-by-one $NetBSD revision numbers since those are what were checked in
during the commit of the current revision).

It would probably be a good idea for _ALL_ of the files in the NetBSD
CVSROOT directory to be shipped with the repository (i.e. all the RCS
files _and_ the checked out copy that CVS will actually read when
accessing the repository) regardless of how it is accessed (FTP, rsync,
CVSup, etc.).  (I've asked for this many times before but it never seems
to happen....)

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>