[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: Derek Robert Price
Subject: Re: CVS_LOCAL_BRANCH_NUM feature
Date: Wed, 05 Mar 2003 12:00:20 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02

Mark D. Baushke wrote:

I consider that committing to the mainline CVSROOT/config file in the
sure knowledge that it may be stomped by the master repository seems an
iffy proposition.

CVSup will merge your mainline repository CVSROOT and CVSROOT/config,v
and CVSROOT/config although it may (or may not -- depending on the CVSup
configuration) lose the CVS_LOCAL_BRANCH_NUM value in the checked out
CVSROOT/config file until such time as the CVSROOT has any other commit
to cause the mkmodules() to rebuild the checked out administrative

This kind of collision with the master respository and possible results
of losing the configuration seems less than robust to me.

It is a reason.

That's a good reason. In fact, I might _avoid_ putting the configuration option in CVSROOT/config for that reason and the fact that I don't know nay use for CVS_LOCAL_BRANCH_NUM except CVSup.

A reason to keep the env variable is that there are many "HOW TO"
documents out there which are not getting updated very often that are
associated with CVSup and getting them all updated will take time. For
now, if folks use the cvs 1.12 sources (from cvs or after release), they
will be able to have a recipe that works properly with CVSup.

It is another reason, but perhaps not as good as the first reason.

That's a reason, though I agree not as good as the first since those same documents will still tell users to try and apply the patch. Still, it shouldn't hurt to allow both an env variable and a command line option to set this.



Email: address@hidden

Get CVS support at <http://ximbiot.com>!
160. I'm not a complete idiot - several parts are missing.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]