use make and version control system for every project?

Holger Krekel pyth at devel.trillke.net
Mon Oct 6 08:10:52 EDT 2003


Carl Banks wrote:
> Ben Finney wrote:
> > On Mon, 06 Oct 2003 03:08:57 GMT, Carl Banks wrote:
> >> I recommended not bothering early on because I tend to move files
> >> around quite a bit early on (a major pain in CVS), and I suspect I'm
> >> not the only person to do that.
> > 
> > That's a flaw of CVS, not of revision control.  Other revision control
> > systems (Arch, Subversion, even RCS) don't suffer from this flaw; use
> > any of those to have *no* excuse not to use revision control from the
> > project's inception.
> 
> Well, I've never used Arch or Subversion, so I can't evaluate them.
> I'd expect too much moving files around to be a headache in general
> (even if the system used is a lot better than CVS), but maybe those
> other systems make it effortless.  (shrug).
 

JFYI, subversion makes this quite effortless because it basically
is a transactional filesystem.  'svn mv' will work just like 'mv'
in unix when you are moving stuff around in your working-copy. Of
course, you still have to commit 'svn ci' to make the moves 
persistent. 

cheers, holger





More information about the Python-list mailing list