UW LSST Subversion Repositories

The University of Washington LSST Group keeps maintains the following subversion version control repositories:

• Algorithms: svn://ostrogoth.astro.washington.edu/alg/trunk/
• Documentation: svn://ostrogoth.astro.washington.edu/doc/trunk/
• Pan-STARRS testing:svn://ostrogoth.astro.washington.edu/pstest/trunk/
• Photpipe Pipeline:svn://ostrogoth.astro.washington.edu/photpipe/trunk/

Subversion Clients

To check out code you will need a subversion client. UW linux users can put ~/rowen/local/bin on their path to get one. You can download command-line clients for all platforms from the subversion home site. Mac users wanting a GUI may wish to try svnX. Windows users wanting a GUI may wish try TortoisSVN.

Documentation

CVS users should start with The Top Ten Subversion Tips for CVS Users.

Version Control with Subversion is an excellent manual. This can be read on-line for free or purchased as a normal paperback. It is very readable and includes an excellent introduction and a section for people who are familiar with CVS.

Hints

• After you check out your first repository, please edit ~/.subversion/config and add .pyc and .pyo to global-ignores. Be sure to uncomment both that line and the line [miscellany] above it. The resulting section of file will look something like this:

  [miscellany]
  global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store *.pyc *.pyo *.wpu build
  

  This avoids checking in python bytecode files.

• Check out the current developmental version with svn checkout svn://ostrogoth.astro.washington.edu/project/trunk. Please don't forget the final /trunk or you'll get all revisions!
• List tagged releases with svn ls svn://ostrogoth.astro.washington.edu/project/tags and check one out by appending the desired version.
• If you just want a copy to use (but not modify and check back in) use svn export instead of svn checkout. Exported copies do not have extra subversion files in .svn directories.
• Always move and delete version-controlled files using svn commands, rather than just telling the operating system to do it. That way subversion will know what happened to the files.
• svn mv (or move, ren or rename) will rename a file or folder. This renames the file in your working copy immediately, and renames it in the repository when you commit your changes.
• svn rm (or rem, del or delete) will delete a file or folder. Warning: this deletes the file from your working copy immediately, and "deletes" it from the repository when you commit your changes (though of course it's not really deleted from the repository, but it is no longer part of the code for the checked in version).

Local

Setup and maintenance of our repositories.