|
From: | Sonam Chauhan |
Subject: | Re: Problems using CVS transparently |
Date: | Fri, 05 Apr 2002 14:50:39 +1000 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120 |
Yuval Rotem wrote:
-----Original Message----- From: address@hidden [mailto:address@hidden Behalf Of Sonam Chauhan Sent: Thursday, April 04, 2002 7:46 AM To: address@hidden Subject: Re: Problems using CVS transparently ... Basically I need CVS only for versioning capabilities. Before a major release, I'd like to do something like this (params are wrong - I have no idea) "cvs -tag -recurse -tag_name "Release Number 9" <souce-controlled-dir> I could then use CVS to restore the directory or even specific file to previous release checkpoints. ... -----End of Original Message If that's all you need, is it really worth the trouble of integrating with CVS? Why not just tar all your files at each release point and keep it somewhere? Whenever you want you can extract a file, a directory or the whole tree, diff between releases, etc.
Tarring an entire directory can be wasteful since the directories have code and data.
CVS is more efficient at storage (IIRC, even with binary files, it only stores new copies if the file has changed. And much of the code is text)
(Personally I would rather use a good source control system and some other tool for deployment, but I guess that's not an option here).
Hmm, do you have some recommendations for some good tools? Sonam
Yuval. _______________________________________________ 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
[Prev in Thread] | Current Thread | [Next in Thread] |