Re^2: Learning How to Use CVS for Personal Perl Coding Practices

First of all, learn subversion first: it's the future.

Whenever I hear someone say "Use XXX, it's the future", I think "there's a quack selling vaporware as snake oil".

Usually, when I look at using a piece of software, I have a problem I need to solve now - I don't need something that will solve my problems at some unspecific time in the future.

If you want to pitch subversion, sell it on its merits. "It's the future" is meaningless.

Perl --((8:>*

Comment on Re^2: Learning How to Use CVS for Personal Perl Coding Practices

Replies are listed 'Best First'.

Re^3: Learning How to Use CVS for Personal Perl Coding Practices
by tphyahoo (Vicar) on Nov 03, 2005 at 10:59 UTC

All right, all right.

"So what's wrong with CVS? Because it uses the RCS storage system under the hood, CVS can only track file contents, not tree structures. As a result, the user has no way to copy, move or rename items without losing history. Tree rearrangements are always ugly server-side tweaks......

......

In 1995, Karl Fogel and Jim Blandy founded Cyclic Software, a company for commercially supporting and improving CVS. Cyclic made the first public release of a network-enabled CVS (contributed by Cygnus software). In 1999, Karl Fogel published a book about CVS and the open-source development model it enables (cvsbook.red-bean.com). Karl and Jim had long talked about writing a replacement for CVS; Jim even had drafted a new, theoretical repository design. Finally, in February 2000, Brian Behlendorf of Collabnet (www.collab.net) offered Karl a full-time job to write a CVS replacement. Karl gathered a team and work began in May.

The team settled on a few simple goals: it was decided that Subversion would be designed as a functional replacement for CVS. It would do everything that CVS does, preserving the same development model while fixing the flaws in CVS's (lack of) design. Existing CVS users would be the target audience; any CVS user should be able to start using Subversion with little effort."

As always, your milage may vary. But that's what I meant about "future."

[reply]


Just another Perl shrine
	PerlMonks