[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problems using CVS transparently
From: |
Sonam Chauhan |
Subject: |
Re: Problems using CVS transparently |
Date: |
Thu, 04 Apr 2002 17:07:09 +1000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120 |
Pierre Asselin wrote:
In <address@hidden> Sonam Chauhan <address@hidden> writes:
PROBLEM #1: CVS usage must be transparent. This means no 'CVS'
meta-directories are allowed [ ... ]
Give up now before you get an ulcer?
OK.
SOLUTION #1: The way I solved this problem (I think) was by creating
a parallel source controlled directory hard linked to the development
hierarchy.
Does that work? CVS has a way of ignoring files with link count
greater than 1.
It didn't work well below the top level linked subdirectories. Is this what you
thought would happen?
Anyway, I've given up on it.
General impression: you can have your development environment or you
can have CVS, and you can't have both.
That sounds about right :)
Maybe you should treat your dev environment as a virtual vendor.
Export trees, not checkout, to use in development. When ready,
import them back, not commit, into CVS, as if you were releasing
a tarball to yourself. This is an extremely clumsy way to use CVS,
turning it into a glorified closet. It also means that you develop
without the benefit of a source-controlled environment: no cvs diff,
no cvs update, etc.
I was thinking of trying another approach: the IDE treats each code directory
as a "code package" . Typically I may only need to release code in 2 or 3 of 15
packages - say dir11, dir22, and dir 55. The IDE just zips up these
directories. Each ZIP file is sent to remote servers and unzipped there.
What I was thinking of doing was to do this:
1. Create a copy (no hard links now!) of the working directory.
Check the copy into CVS. Delete the copy.
2. For every release, checkout the module, unzip the released ZIP files
onto the checked out directory, (a similar process takes place on
the servers during the actual release)
3. cvs-commit the entire thing. I'm not clear if I could create a
new tag though.
Sonam
_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs
--
Electronic Commerce
Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Fax: +61-2-9335-0753
- Problems using CVS transparently, Sonam Chauhan, 2002/04/03
- Re: Problems using CVS transparently, Pierre Asselin, 2002/04/03
- Re: Problems using CVS transparently,
Sonam Chauhan <=
- Re: Problems using CVS transparently, Sonam Chauhan, 2002/04/04
- RE: Problems using CVS transparently, Yuval Rotem, 2002/04/04
- Re: Problems using CVS transparently, Eric Siegerman, 2002/04/04
- Re: Re: Problems using CVS transparently, Kaz Kylheku, 2002/04/04
- Re: Problems using CVS transparently, Sonam Chauhan, 2002/04/04
- Re: Re: Problems using CVS transparently, Joi Ellis, 2002/04/05
- Re: Re: Re: Problems using CVS transparently, Kaz Kylheku, 2002/04/05
- Re: Re: Re: Problems using CVS transparently, Eric Siegerman, 2002/04/05
Re: Problems using CVS transparently, Pierre Asselin, 2002/04/04