Perl Monk, Perl Meditation | |
PerlMonks |
Re^2: Learning How to Use CVS for Personal Perl Coding Practicesby Rhose (Priest) |
on Nov 03, 2005 at 15:13 UTC ( [id://505385]=note: print w/replies, xml ) | Need Help?? |
While there is nothing incorrect with your example, I've followed the suggestion of using trunk, tags, and branches, and have found it to be very helpful. (Use branches for parallel development... like migrating code to a new platform while development continues on the current one. Use tags for "point in time" snapshots.) I use this structure even for repositories for which I'm *sure* I'll never need them. (If, for no better reason, than to always know I need to check out the trunk on any given repo.)
You set this up before the initial import. Create a directory (let's assume /home/rhose/svn). In this directory, create three more directories -- trunk, tags, and branches. Place all your directories/code in the trunk directory.
You are now ready to import. (Please note, I'm using the Subversion daemon in this example.) svn import /home/rhose/svn svn://myserver/myrepo -m "Initial import" You are now free to nuke your import structure, checkout the trunk, and start working. Also, I like to make a temporary copy of the original files until I verify the repo import worked correctly and everything is in there... I've never had a problem, but I tend to play it extra safe. (Please note... once you check out a repo, do NOT mess with the .svn directories -- like Bruce Banner, you'll not like them when they're angry.)
If you are in a Windows environment, I'd like to second tphyahoo's advice -- TortoiseSVN is wonderful.
In Section
Seekers of Perl Wisdom
|
|