info-cvs
[Top][All Lists]
Advanced

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

Re: general organization of CVS modules


From: Alexander Kamilewicz
Subject: Re: general organization of CVS modules
Date: Thu, 19 Apr 2001 11:01:36 -0500

Fran Fabrizio wrote:
> 
> 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?

cd /usr/local/apache
cvs co -d cgi-bin my-project/cgi-bin
cvs up -d cgi-bin

Sorry, I can't help with #2.



reply via email to

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