About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
legacy:vufind_1.x_developer_manual:subversion

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
subversion [2012/04/03 15:52] katwollegacy:vufind_1.x_developer_manual:subversion [2015/12/11 20:14] – ↷ Page moved from subversion to legacy:vufind_1.x_developer_manual:subversion demiankatz
Line 25: Line 25:
  
 ===== Initial Checkout ===== ===== Initial Checkout =====
-You check out code from a Subversion repository when you plan on changing it and want to keep track of its history. There are several popular Subversion clients that simplify the checkout process, including [[eclipse setup|Eclipse (with Subclipse)]], [[http://tortoisesvn.net/|Tortoise SVN]] and [[http://www.rapidsvn.org/|Rapid SVN]].  If you don't want to use a fancy graphical tool, there's also the good ol' command line.+You check out code from a Subversion repository when you plan on changing it and want to keep track of its history. There are several popular Subversion clients that simplify the checkout process, including [[https://marketplace.eclipse.org/content/subclipse|Eclipse (with Subclipse)]], [[http://tortoisesvn.net/|Tortoise SVN]] and [[http://www.rapidsvn.org/|Rapid SVN]].  If you don't want to use a fancy graphical tool, there's also the good ol' command line.
  
 ==== Command Line Checkout ==== ==== Command Line Checkout ====
Line 105: Line 105:
  
 Regardless of which approach you take, once you are done, you are all set to begin using the [[subversion#vendor_branching|Subversion vendor branching strategy]] to keep things up to date.  If you want to stay on the cutting edge, you should get into the habit of keeping up to date with the trunk -- the more often you merge, the less painful the process should be!  Get involved with the [[https://lists.sourceforge.net/mailman/listinfo/vufind-tech|vufind-tech]] mailing list so that you can ask questions about recent changes and be involved in discussions of major changes to the software. Regardless of which approach you take, once you are done, you are all set to begin using the [[subversion#vendor_branching|Subversion vendor branching strategy]] to keep things up to date.  If you want to stay on the cutting edge, you should get into the habit of keeping up to date with the trunk -- the more often you merge, the less painful the process should be!  Get involved with the [[https://lists.sourceforge.net/mailman/listinfo/vufind-tech|vufind-tech]] mailing list so that you can ask questions about recent changes and be involved in discussions of major changes to the software.
 +
 +===== Other Subversion Resources =====
 +
 +  * [[http://tortoisesvn.net/ssh_howto.html|Securing Svnserve using SSH]] - If you want to allow secure access to your local SVN repository, this tutorial will help.
 +    * If using Subclipse on Windows, you may also need [[http://www.woodwardweb.com/java/000155.html|this article]].
 +  * [[https://www.zulius.com/how-to/automatically-update-a-subversion-working-copy-on-commit/|Automatically update a Subversion working copy on commit]] - If you want to use SVN to automatically update your code on a server, this will help (though obviously you should only do this if you know what you are doing!).
  
 ===== Using Git ===== ===== Using Git =====
legacy/vufind_1.x_developer_manual/subversion.txt · Last modified: 2018/12/19 15:00 by demiankatz