I upvoted you because I used to be like you ;) And then I switched to CVS and haven't looked back since.
Even though I am the only Perl programmer here, version control does have a habit of saving my ass, no matter how careful I think I'm being. And once you're used to it, it's no more difficult than copying your files around. Actually, I find it less so.
Next project I'm off to try Subversion. . . ;)
But seriously, even if you're the only Perl programmer, give CVS or Subversion a look. Easy to use, easy to get going, and easy to be productive. You'll be happy you did.
Cheers!
MrCromeDome | [reply] |
Actually I've been trying to impliment some form of RCS since I started working (as a programmer) but haven't got the okay yet (got to love management). However, the new project I'm working on might give me an excuse to use some RCS (CVS proably) - here's hoping.
Update: I get to try RCS, CVS, and Aegis on a new test server, if this poll is still active I'll post which is my fav. of these three
"Cogito cogito ergo cogito sum - I think that I think, therefore I think that I am." Ambrose Bierce
| [reply] |
Who needs management permission? If you're the only developer, concurrent editing isn't a big problem, so just install something locally on your machine.
I was the sole perl guy at my work this past summer, so I installed TortoiseSVN (a Windows Subversion package) on my first day and used it locally while I was there. Simple as hell to use, and had nothing to worry about when I accidently deleted important files. Plus, it made versioning so much easier, just use the SVN version. :)
Update: looks like I'm preaching to the converted. Congratz
| [reply] |
I used CVS for some years now and recently switched to Subversion.
I was surprised that the commands for ci, co, etc. are identical to the cvs commands -- no re-learning:
$ cvs ci
[...]
$ svn ci
[...]
But, there are additional commands like svn mv.
The only difference I noted (but I use SVN/CVS only as an "intelligent backup", no more advanced things) is the way you create a new repository, but there's an excellent quickstart guide (link lost).
I couldn't imagine developing without using some kind of version control system -- it's much easier to use than cp/scp/tar/rsync :) | [reply] [d/l] |
Using version control has nothing to do with the number of people working on the code. Everything I do goes in version control.
| [reply] |
Okay I can now say I like RCS the best (at least for my needs), it's simple and quick - and works a whole lot better then cp -rp ;).
"Cogito cogito ergo cogito sum - I think that I think, therefore I think that I am." Ambrose Bierce
| [reply] |