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.

cd /home/rhose
mkdir svn
cd svn
mkdir trunk
mkdir tags
mkdir branches
cd trunk
cp /home/rhose/work/project123/* .
[download]

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.)

cd /home/rhose/svn
rm -rf *
cd /home/rhose/work
mv project123 project123.save
mkdir project123
cd project123
svn checkout svn://myserver/myrepo/trunk/ .
vi mycode.pl
svn commit -m "Made change XXX for project YYYY"
cd ..
rm -rf project123.save
[download]

If you are in a Windows environment, I'd like to second tphyahoo's advice -- TortoiseSVN is wonderful.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.