[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: general organization of CVS modules

From: Mike Klinke
Subject: Re: general organization of CVS modules
Date: Fri, 13 Apr 2001 18:45:13 -0500

Rather than try to marry CVS and your production structure why not use some
intermediate script or batch/JCL system to translate from whatever CVS
structure you find most convenient to whatever your production structure
needs are? Seems like you could have the best of both worlds.

Regards, Mike Klinke

-----Original Message-----
From: Fran Fabrizio <address@hidden>
To: address@hidden <address@hidden>
Date: Friday, April 13, 2001 3:18 PM
Subject: general organization of CVS modules

>Hello all,
>I have a couple of general questions.
>1.  Say I have a web project that consists of some CGI scripts and some
>static pages.  The CGI scripts are in /usr/local/apache/cgi-bin/, the
>static pages are in /usr/local/apache/htdocs.  I want to make it all one
>module since logically they are related, but it seems unwieldy.  The
>shared parent directory is /usr/local/apache, but clearly I would not
>want the project to be based there, as there are also several unrelated
>directories underneath that directory (conf, logs, etc...).  How does
>one organize this neatly?  Is there a way to say 'cvs co my-project' or
>'cvs update my-project' while in /usr/local/apache and have it just
>checkout/update those two directories?
>2.  Say I have a project at /home/me/project/.  This project has some
>data directories like /home/me/project/saved-messages/.  I want to put
>project under CVS, but I don't want to include the saved-messages
>subdir.  I know I can import the 'project' directory and then set up an
>alias in the modules file to have a way to checkout and ignore the
>'saved-messages' directory, but is there a more elegant way?
>Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]