im going to blog my specific experiences here in this SVN specific blog.
I downloaded a version of SVN called Collabnet - after installing it - i have a program group called CollaNet Subversion Server (1.5).
Im reading throught he svn-book (pdf) avail upon install, pretty good. 385 pages
Im down with the concepts of the repository, working copy, commiting (checking in), updating(checking out), conflict resolution, automatic mergs etc. Ive been using another repository for years, that has a nice GUI.
My first official command, after testing a few of the help commands, using the command prompt, was to CREATE THE REPOSITORY. This is the central location that i would create a working copy from. I used the SVN admn command, from the command prompt.
svnadmin create /SVN/repositories/DM
I needed to first create that directory at this path, it did not do that for me. The command line simply retured the prompt after doing its work - no message about fails or anything else! I like it already.
I browsed to the path and opended the DM folder, and wala - there are 4 new folders in it
conf
db
hooks
locks
and a couple files, including a readme.txt that i opened and read that states
"This is a Subversion repository; use the svnadmin tool to examine it. do not add, delete, or modify here unless you know how to avoid corrupting the repository."
funny...ill read the manual, dont worry. I can say that what i think i have to do next is to copy the intial directors into the repository using the svn commands. Thats how we will *populate the repository - not just by copy and paste, drag and drop. Im sure the svn admin needs to create some additional info that will happen when we use the svn add "somepath" command.
Ok - since i had success creating my initial repos on my c drive - i went ahead and created a new repos on my shared network drive. Makes sense, so i can get to it from a couple different places, plus the network drive is backed up. Piece of cake, no problems. Once i ensured my mapping was active to my network drive, and it could find the letter i was using, boom. There it is. I will work now toward populating the repository with my DM collection that is in the process of being whittled...
The actual command is import - svn import...
Here is the actual command, after about 30 minutes of farting around with this....
I imported first to my local repository, on a smaller scale - to get the hang of it...sure - rather than trying to create a big honkin collection.
i created a repository first at svn/repositories/dm
then i change to the folder where i wanted to import from wwwroot/listeners
then i issed this command, compete with the -m "message" and with trunk at the end
svn import -m "importing" file:///svn/repositories/dm/trunk
then i saw the 9 files from that directory added to the repository. with the reassuring text upon completion of Committed revision 1.
