RE: CVS User Variable Expansion (correction 2)

[Jeff Wood]

Let me try this one more time:

The cvs invocation below should be:

`cvs -s CVSWORKBASE=$CVSWORKBASE checkout qtinc'

-----Original Message-----
From: Jeff Wood [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 9:16 AM
To: CVS Interest (Post)
Subject: CVS User Variable Expansion (correction)

Correction --

The cvs invocation below should be:

`cvs -s $CVSWORKBASE checkout qtinc'

-----Original Message-----
From: Jeff Wood [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 13, 2002 8:49 AM
To: CVS Interest (Post)
Subject: CVS User Variable Expansion

Hi,

 

I have a couple of beginner questions:

 

1) Should CVS user variables be recognized and expanded in the cvs

   modules file?

 

2) If so, what might prevent that from happening on a Linux RH 7.1

   system?

 

In order to provide a little flexibility with regards to the base

address of the working directory, I am attempting to set up a modules

file that would look something like:

 

`qtinc -d ${=CVSWORKBASE}/qt-2.3.1/include xproj/qt-2.3.1/include'

 

Then, I figured I could invoke cvs with something like:

 

`cvs -s $CVSWORKBASE qtinc'

 

In the modules file CVSWORKBASE would be the cvs user variable passed

from the command line.  In the case of the cvs invocation from the

command line the CVSWORKBASE would simply be environment.

 

So, WHERE THE *()@*# AM I GOING WRONG?

 

Is there a different/better way to not hardcode the base address of

the working directory for a checkout?

 

THX,

- Jeff