[cvsnt] Help creating a custom module (modules or modules2)

[Kerry, Richard]

My recollection of trying out modules and modules2 is that modules is
something that only acts on Check-out, but that modules2 is much better
integrated (although not perfectly so).

If you use modules you can do a Check out and you'll get what you
expected.
However if you then do an Update, everything else in the given folders
from the repository appears.

If you use modules2, this problem does not arise, ie you just get the
latest versions of the things the modules2 module specifies.

There are some issues with modules2.
One that caught me out is that it doesn't cope with things at the top
level of the repository (I think it's that way round, it's a while since
I tried it).
I didn't try rtag, you'd need to experiment.

And if you're trying to use Cruise Control, I believe there have been
recommendations not to do so (as it repeated status requests slug the
server) but to use CVSNT's make integration features to get builds done
when changes are recognized.  I've never tried this so I'll leave others
to clarify the technique.

Helpfully,
Possibly,
Richard.


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Glen Starrett
Sent: 08 February 2007 00:07
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Help creating a custom module (modules or modules2)

Matt Schuckmann wrote:
> The problem with the modules mechanism is once the sandbox is created 
> cvs seems to forget all about the Build module and if you do something

> like "cvs up -d" (which our build tool does) in the Build directory it

> goes and checks out all the directories I didn't want created and that

> makes the sandbox much bigger than is needed and makes the build tool 
> run much slower.

I think that's because of the way CVS handles the modules (and modules2)

files -- they are really an alias for additional work on the command 
line at checkout and not really used after that.

I believe the EVS project is getting a better handle on this type of 
system virtualization.  You might want to grab a copy and see how it's 
coming along to give some early feedback, to make sure your needs are
met.

> At this point I'm ready to give up and go back to a hand rolled
checkout 
> and update script but I thought I'd ask the community to see if I'm 
> missing something and if there is a way to make it work with either 
> modules or modules2.

I might suggest you tear your physical structure down even further -- 
down to individual modules that you then reassemble into with modules[2]

into both the current structure (I assume the current physical structure

is being used) and into the desired build structure.  That should 
probably work (but I haven't tried it).

-- 
Glen Starrett
Technical Account Manager, North America
March Hare Software, LLC

http://march-hare.com/cvspro/
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt