[cvsnt] Trouble with ampersand modules

Warren, Erik Erik.Warren at delta.com
Fri May 2 16:51:06 BST 2003


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Bryce,

I had exactly the same situation as you.
How do I include common code in many modules?
I also started out trying to make modules the same way you did.
I found that for me this module definition scheme works:

common software/product-name/common
proc_1 software/product-name/proc_1
ampproc_1 &proc_1 &common

When I check this ampersand module out in my C:\work directory I get:
C:\work\ampproc_1\
------------proc_1\
------------common\


Erik W. Warren
Sr. Engineer - Flt. Ops. Engineering
Delta Air Lines
Dept. 088
P.O. Box 20706
Atlanta, GA 30320-6001
Ph (404) 715-7229
fax (404) 715-7202
erik.warren at delta.com



-----Original Message-----
From: Bryce Schober [mailto:bryceman at dpzone.com]
Sent: Thursday, May 01, 2003 8:48 PM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Re: [cvsnt] Trouble with ampersand modules


OK, guys...  Is nobody listening, or is it just that nobody cares?

Bryce Schober wrote:

> I'm a newbie cvs admin (yeah, I know...  everyone run in horror!) 
> having troubles getting any ampersand module to work.  We'd like to 
> share common lib files across project directories, and from my 
> searching around, I figured ampersand modules were the best way to do 
> it.  So I set up a test respository that looks like the one we want to 
> use with this kind of structure:
>
> software/
> ---product-name/
> ------common/
> ------proc_1/
> ------proc_2/
>
> So what I _really_ want is to have selected files from "common" check 
> out in the root of proc_1 & proc_2, but I gather from the docs that 
> the best I can get is to have them in a subdir of proc_1 & proc_2, so 
> I'll settle for that.  So I made my modules file as follows:
>
> common software/product-name/common
> proc_1 software/product-name/proc_1 $common
>
> Using this setup, the "common" module checks out as expected, but 
> checkout of the proc_1 module fails, giving me this error (using both 
> wincvs and cvs):
>
> cvs server: warning: new-born proc_1/$common has disappeared
>
> I'm using cvsnt 2.0.2.
>
> Thanks,
> Bryce Schober
>
> ---
> [This E-mail scanned for viruses by digiposs.com]
>
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs
> ---
> [This E-mail scanned for viruses by digiposs.com]
>

---
[This E-mail scanned for viruses by digiposs.com]

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook