1. There are actually *two* repositories -- one for the OSCAR code and one for everything else (old web site records, OSCAR papers, etc.).
2. The URLs for anonymous / read-only checkouts are:
svn://svn.oscar.openclustergroup.org/oscar/
svn://svn.oscar.openclustergroup.org/oscar-data/*** Do *NOT* check these URL's out directly -- see below.
3. The URLs for developer / writable checkouts are:
svn+ssh://svn.oscar.openclustergroup.org/l/svn/oscar/
svn+ssh://svn.oscar.openclustergroup.org/l/svn/oscar-data/*** Do *NOT* check these URL's out directly -- see below.
4. Go read the SVN docs. http://svnbook.red-bean.com/
5. Per my mail to the core group the other day, you must have an account at Indiana University to have writable access. If you're an OSCAR core member and do not have an IU account, mail me, and we'll get it set up. Easy to do (please be sure to have your on-line banking ready to transfer the setup fees to my Swiss bank account).
6. Tim finally wrestled register.com to the ground for a ten count; we're now in the propagation delay time to switch openclustergroup.org's DNS to IU. Once your site updates, you'll be able to see the DNS name "svn.oscar.openclustergroup.org". If you have a burning desire to get a checkout before then, you can use the hostname "svn.osl.iu.edu".
7. Go read the SVN docs. http://svnbook.red-bean.com/
8. I imported all of OSCAR's CVS history. I used the standard SVN community convention -- there are three top-level directories in each of the two repositories: trunk (analogous to the CVS HEAD), tags (for all the tags), and branches (for all the branches). WHEN YOU CHECKOUT, you typically ONLY want to checkout the trunk. For example:
svn co svn+ssh://svn.oscar.openclustergroup.org/l/svn/oscar/trunk oscar
This checks out the trunk and puts it into a local directory named "oscar". If you check out the entire repository, a) be sure you have enough disk space, and b) be sure you have obscene amounts of bandwdith, and c) start reading Moby Dick; it'll take a while.
9. There are no such things as real "tags" or "branches" in Subversion -- since it's a database back end, you simply copy an entire repository tree from one directory to another to effect a tag or branch. The copy in the database is lazy, so there's actually very little space taken up by a tag/branch. This is why we have 3 top-level directories (trunk, tags, branches). Note that these directory names have no special meaning to Subversion -- they're just directories, like any other. Here's the conventions that we follow:
- the trunk is where active development occurs
- branches is where all official branches go; when we release, we simply copy the trunk into the branches directory. Development can continue on those branches, if desired.
- tags is where all official tags go; when we release, we simply copy the trunk into the tags directory. BY CONVENTION: we NEVER write into those trees again.
10. You will likely need to download and install a Subversion client; it's so new that it hasn't really started showing up in distros yet. http://subversion.tigris.org/ is where you want to go -- be sure to scroll down to the bottom of the download page to get the latest releases. At the time of this writing, v1.0.6 is the most recent stable version, but I've had good luck with 1.1rc1.
11. Go read the SVN docs. http://svnbook.red-bean.com/
12. Subversion was designed to be easy for long-time CVS users. The single hardest thing to master is typing "svn" instead of "cvs".
13. Remember that SVN supports atomic commits -- so when you have 16 files to commit in different directories, it is better to commit them all at once rather than piecemeal / by directory (like CVS does, whether you wanted to or not).
14. There's no need to worry about telling SVN that an RPM is a binary file; it'll just figure it out when you "svn add foo.rpm".
15. Unlike CVS's "diff" operation, "svn diff" is a local operation -- you don't have to have network access to run it. Also, "svn status" is your friend -- use it to see what you need to update instead of "cvs up" (the old way ;-) ).
16. Go read the SVN docs. http://svnbook.red-bean.com/
17. Also don't forget your new friends:
- svn mv (move)
- svn rm (remove)
- svn cp (copy)
- svn revert (ditch all your local changes and revert to a clean repository copy)
That's it for now; be sure to let me know if you have any questions! (Go read the SVN docs: http://svnbook.red-bean.com/)
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
