[cvsnt] Ampersand modules and 2.0.1a

Wed Apr 16 17:27:07 BST 2003

Ok, my example was a little bit incorrect. Let me try again. In my modules
file 
I have definitions like
 mod1 -d Dir\SubDir1    includeDir1
 mod2 -d Dir\SubDir2    includeDir2
 mod3 -d Dir\SubDir3    includeDir3

These are all regular modules. Now I build an Ampersand module in the
modules
file like this
 AmpMod    &mod1 &mod2 &mod3

Checking out the module "AmpMod" (cvs co AmpMod) gives the following
directory
structure on the client:

 AmpMod
   |
   +-Dir
      +-SubDir1
      +-SubDir2
      +-SubDir3

This is how it works for me with version 1.11.1.3-72.
With version 2.0.1a using the same command I get the following
directory structure on the client:

 (null)
   |
   +-mod1
   +-mod2
   +-mod3

So in the newer version directories are created under the toplevel dir
corresponding to the name of the regular modules mod1 - modn ignoring
their -d option. For me this is the important difference.

I hope I could make my problem clear.
Sven

Tony Hoyle wrote:

> On Wed, 16 Apr 2003 14:53:34 +0200, "Issberner, Sven 3767 S-PP-RD-E3"
> <Sven.Issberner at heidelberg.com> wrote:

> >With server version 2.0.1a the same commands result in a completely =
> >different
> >working copy :
> >
> >"cvs co -d MainXXX mainmod1" gives:
> >
> >	  MainXXX
> >          |
> >          +-__submod1
> >          +-__submod1
> >          +-__submod1

> That's correct.  The null thing will be fixed in the next release.  That's
how
> it's documented to work, and seems correct to me...

> >So it seems to me that the -d option in the modules file is ignored.
> >As we rely on the behaviour of version 1.11.1.3-72 the new version
> >is unusable for our department. It would be nice if you could reenable
> >this behaviuor.

> -d isn't supposed to work with ampersand modules (there's no sensible way it
> could work, either, since you're using two mutually incompatible options to
> change the module location).  It sounds like you should be using aliases.

> Tony