[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Two directories for one project or module
From: |
Adrian Constantin |
Subject: |
Re: Two directories for one project or module |
Date: |
Sun, 20 Jun 2004 14:06:00 -0700 (PDT) |
--- Kenneth Dombrowski <address@hidden> wrote:
> On 04-06-20 09:49 -0700, Adrian Constantin wrote:
> > ...
> >
> > I was thinking of having a sandbox directly within
> the DocumentRoot.
> > If I import the up-dir, which include the working
> and
> > the public directories, then when I check out I
> end up
> > with the working directory included somewhere
> under
> > DocumentRoot.
> >
> address@hidden:~/cvs/test$ cvs
> -d:ext:cvs.ylayali.net:/var/cvs/ylayali.net checkout
> -d htdocs
> dev/htdocs
> address@hidden:~/cvs/test$ ls -l
> total 4
> drwxr-sr-x 18 kenneth kenneth 4096 Jun 20
> 13:13 htdocs
...
> the main thing being that it's fine to check out a
> subset of a module
> (/dev/htdocs)
>
> the other thing to notice being the '-d htdocs'
> alias, without that the
> checkout would have created the intermediate 'dev'
> directory
>
> Is that any closer?
This might actually work! :)
Will susequent updates know they have to do with
only a part of the module ? Can I also release a
part of the module ?
Does anyone has an ideea as how can I have the
public directory kept clean, that is without the CVS
subdirectory ? Can I move the CVS subdirectroy out
of the sandbox ? I would need something like
'cvs release' but that would actually do a patch.
Currently I use cvs diff and then patch so that I
can have a clean directory on the web server. But
like this I have to remember the last tag that I
patched in the public directory last time. I
do not want to 'cvs release' and overwrite everytime
since I do not make many changes between commits and
the site is big.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com