Re: CVS 1.11.6: export bug in CVS on (LI/U)nix when CVSROOT env contains trailing slash

[Mark D. Baushke]

Paul Edwards <kerravon@nosppaam.w3.to> writes:

> I don't know the solution to the problem, 

I have not yet looked closely at this bug report... so, no comments
about that right now.

> but I am surprised that "-d" overrides the CVS/Root files.

See http://www.cvshome.org/docs/manual/current/cvs_2.html#SEC10

| The -d option and the `CVS/Root' file both override the $CVSROOT
| environment variable. If -d option differs from `CVS/Root', the former
| is used. Of course, for proper operation they should be two ways of
| referring to the same repository.

> As an end-user, I wouldn't expect it to make any difference how I
> specified my CVSROOT, I would expect the same behaviour.

The -d switch is very useful when the user has checked their sources out
of a cvs mirror and are now ready to do a final update and/or commit to
the master repository.
 
> I think the behaviour of "-d" is the one that is incorrect,

I believe that yours is a minority opinion in this case.

> overwriting the CVS/Root files.

s/overwriting/overriding/

The -d option does not over-write the CVS/Root file.

> Who's to say that I don't want to change my access method to
> a remote repository, but put that into the CVSROOT variable
> rather than specify "-d"?

cvs will ignore your $CVSROOT variable if it sees a CVS/Root
or a -d <root> command-line option, so that is 'who' in this case.

  -d <root> will always override the CVS/Root or $CVSROOT values.
  CVS/Root is a default if the command line is not specified.
  $CVSROOT is a default if no other information is available.

The -d <root> has always overridden the CVSROOT environment variable
goin back at least as far as cvs 1.3. When I added CVS/Root, I put it
in the middle of the two as to precedence.

        Enjoy!
        -- Mark