Re: [RFC] CVS directory structure
| From: | Tobias Schlitt | Date: | Sat, 15 Nov 2003 16:51:35 +0000 |
| Subject: | Re: [RFC] CVS directory structure | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23642@lists.php.net to get a copy of this message | ||
On Sat, 2003-11-15 at 16:13, Pierre-Alain Joye wrote:
> > > I'm -1 on this. CVS is a tool for source control. Doing development
> > > directly
> > > on your CVS dir is a bad idea.
> > That's exactly the point. CVS is initially made for developing inside
> > it's checkout directories. That's just your local copy, which you will
> > commit to the central repository. So copiing files away from your
> > sandbox nd recopiing is double effort, without win.
> Developing here == keeping files history, not run them. Nothing more.
> pear install package.xml should be used, or a little bat to sync the dev
> tree (your running script) and the cvs repo helps.
These are all "littly dirty solutions" which were run over the years.
What is so bad if you do
- check out
- change code
- test
- change code
- test
- commit
instead of
- check out
- copy files
- change code
- test
- change code
- test
- copy files
- commit
???
--
http://www.schlitt.info
http://www.schlitt.info/applications/blog