Trouble with modules file syntax

Lord Bitnerd of Pentium

unread,

Jun 11, 2012, 3:06:33 PM6/11/12

to

I have:

Client: Concurrent Versions System (CVS) 1.12.12 (client)
Server: Concurrent Versions System (CVS) 1.12.13 (client/server)

I am writing a library and want to use it in several places, including client
code, test/development code etc. I am trying to understand the syntax for the
modules file, which I have not been able to figure out yet.

I have library source, which lives in current directory "XXlib" in the
repository (as in "cvs checkout XXlib"). I've developed it with some test code
that lives at

DevCode/PrimeSieve/SieveCalc

and I want the XXlib module to show up (as an alias) at

DevCode/PrimeSieve/XXlib

In other words, when I "cvs checkout DevCode", I want to see SieveCalc and XXlib
modules under DevCode/PrimeSieve.

None of the following attempts in the modules file work:

# Add XXlib to DevCode/PrimeSieve
#DevCode &PrimeSieve &XXlib
#DevCode/PrimeSieve &XXlib
#PrimeSieve &XXlib
#PrimeSieve/XXlib -a XXlib
#DevCode/PrimeSieve/XXlib -a XXlib
#DevCode/PrimeSieve DevCode/PrimeSieve/&XXlib
#DevCode DevCode/PrimeSieve/&XXlib

DevCode/PrimeSieve DevCode/PrimeSieve DevCode/PrimeSieve/&XXlib

Can anybody see the error of my ways and hopefully provide a solution?

--
Harvey <bit...@brydon.net>
No matter how much memory I buy, I keep forgetting things.

Larry Jones

unread,

Jun 11, 2012, 9:50:28 PM6/11/12

to Lord Bitnerd of Pentium, info...@nongnu.org

Lord Bitnerd of Pentium writes:
>
> I have library source, which lives in current directory "XXlib" in the
> repository (as in "cvs checkout XXlib"). I've developed it with some test code
> that lives at
>
> DevCode/PrimeSieve/SieveCalc
>
> and I want the XXlib module to show up (as an alias) at
>
> DevCode/PrimeSieve/XXlib
>
> In other words, when I "cvs checkout DevCode", I want to see SieveCalc and XXlib
> modules under DevCode/PrimeSieve.

That's a tricky thing to do, it's much simpler if you add the library at
the top level instead (i.e., DevCode/XXlib). That's just:

DevCode DevCode &XXlib

If you really want it at a lower level, you have to define a special
module for it that specifies the directory to check out into:

DevCodeXXlib -d PrimeSieve/XXlib XXlib
DevCode DevCode &DevCodeXXlib
--
Larry Jones

Mom would be a lot more fun if she was a little more gullible. -- Calvin

Lord Bitnerd of Pentium

unread,

Jun 12, 2012, 11:34:45 AM6/12/12

to

On 2012/06/11 20:50, Larry Jones wrote:
> Lord Bitnerd of Pentium writes:
>>
>> I have library source, which lives in current directory "XXlib" in the
>> repository (as in "cvs checkout XXlib"). I've developed it with some test code
>> that lives at
>>
>> DevCode/PrimeSieve/SieveCalc
>>
>> and I want the XXlib module to show up (as an alias) at
>>
>> DevCode/PrimeSieve/XXlib
>>
>> In other words, when I "cvs checkout DevCode", I want to see SieveCalc and XXlib
>> modules under DevCode/PrimeSieve.
>
> That's a tricky thing to do, it's much simpler if you add the library at
> the top level instead (i.e., DevCode/XXlib). That's just:
>
> DevCode DevCode &XXlib
>
> If you really want it at a lower level, you have to define a special
> module for it that specifies the directory to check out into:
>
> DevCodeXXlib -d PrimeSieve/XXlib XXlib
> DevCode DevCode &DevCodeXXlib

Ah bless you - that is exactly what I want. I tried several variations on this
but I couldn't figure out the "-d" syntax.

Thanks very much!