RE: problem with "co -d xx -n" : bug or feature?

[Chris Cameron]

There used to be a patch available at cvshome to fix a similar problem in
the modules file.  I cannot remember the exact details, but we installed the
patch.  AFAIK it has not been incorporated into the main CVS tree.  Sorry I
can't give you any more details, but I'm out of the office, visiting sales
offices in the Americas, so can't get at our CVS repository to give you more
details.

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf Of
> Haefelinger, Wolfgang
> Sent: Friday, 2 February 2001 7:53 a.m.
> To: 'address@hidden'
> Subject: problem with "co -d xx -n" : bug or feature?
>
>
> Hello there,
> here's  my  problem:  defined an "ampersand module"
> in  $CVSROOT/CVSROOT/modules and got a problem when
> checking out the module using checkout options "-d"
> and "-d" and want to know whether this is a (known)
> bug or a feature. That's what I have and what I did
> on
>  $uname -a
>  SunOS intra-dev 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-2
>
>  $cvs --v
>  Concurrent Versions System (CVS) 1.10.7 (client/server)
>
> My repository contains the directories "mod1" and "mod2".
> Want to checkout them both with a symbolic name. There-
> fore I added the line "am &mod1 mod2" to the modules
> file:
>
>  $ cat $CVSROOT/CVSROOT/modules
>  am &mod1 &mod2
>
> That's pretty fine since
>  $ rm -rf am
>  $ cvs co am
>  $ ls am
>  mod1 mod2
>
> does exactly what I want. Even better,
>
>  $ rm -rf xx
>  $ cvs co -d xx am
>  $ ls xx
>  mod1 mod2
>
> let's me checkout the modules in another directory. That's
> wonderful, wow!
>
> BUT, trying also option -n to prevent any additional checkout
> script from beeing triggered behaves unexpected:
>
>  $ rm -rf *
>  $ cvs co -n -d xx am
>  $ ls
>  mod1 mod2
>
> The modules are checked out in the working directory and not
> as beeing told in the subdirectory "xx".
>
> BUT-BUT, on the other side,
>
>  $ rm -rf *
>  $ cvs co -n -d xx mod1 mod2
>  $ ls
>  xx
>
> does the right thing.
>
> Ok, I'm much too stupid to understand why 'cvs' behave in
> this way, therefore  I  ask you, what's going on here. If
> this is a bug, I'm willing to fix it.
>
> Thanks,
> Wolfi.
>
>  _Wolfgang Haefelinger________________________
>  voice: 069-263-16582
>  email: address@hidden
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>