Differences

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

--- subversion [2009/11/13 14:46] – demiankatz
+++ legacy:vufind_1.x_developer_manual:subversion [2018/12/19 15:00] (current) – demiankatz
@@ Line 1: / Line 1: @@
-====== Initial Checkout ======
+====== Subversion ======
-To set up a project, you can use several methods. There are several popular Subversion clients, including [[eclipse setup|Eclipse (with Subclipse)]], [[http://tortoisesvn.net/|Tortoise SVN]], [[http://www.rapidsvn.org/|Rapid SVN]], and the good ol' command line.
+// VuFind development now uses [[development:recommended_tools:git|Git]]. This outdated page has been deleted to prevent confusion. To view old content for historical interest, see the “Old Revisions” list below. //
-===== Command Line =====
-Change to the directory you want to work on your Vufind instance and then run this command
-svn co https://vufind.svn.sourceforge.net/svnroot/vufind/trunk vufind
-This will check out the Vufind source into a folder named vufind.
-  As a side note, don't forget to export the code if you are planning a deployment:
-  svn ex https://vufind.svn.sourceforge.net/svnroot/vufind/trunk vufind
-  This removes the .svn files and will greatly reduce the file size of the package
-====== Vendor Branching ======
-Vendor branching is a useful strategy for merging changes to an external project (i.e. VuFind) with changes to a local project (i.e. your own VuFind-based catalog).  In other words, it's a way of keeping up with external developments without having to rewrite all of your local changes.  To take advantage of this, you need your own Subversion server.  The general idea is that when you set up your project, you should first create a "vendor" directory and populate it with the third party code.  The "trunk" directory that you do your development in should be established as a copy of the "vendor" directory.  Whenever the vendor code changes, you load the latest third-party code into the "vendor" directory and then combine those changes with your customized "trunk" by using Subversion's powerful merging capabilities.  The more often you merge, the easier it will be to keep your customizations intact.
-It sounds complicated at first, but it makes more sense when you understand version control in general.  This is highly recommended if you plan on maintaining a complex VuFind installation over the long term!  For more details, see the [[http://svnbook.red-bean.com/en/1.5/svn.advanced.vendorbr.html|vendor branching]] chapter of the very helpful [[http://svnbook.red-bean.com/|Version Control with Subversion]] book.
 ---- struct data ----
+properties.Page Owner :
 ----