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.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
subversion [2010/11/17 14:07] – demiankatz | subversion [2012/04/03 15:50] – Checkout to create working copy katwol | ||
---|---|---|---|
Line 4: | Line 4: | ||
You can use Subversion at several levels: you can [[subversion# | You can use Subversion at several levels: you can [[subversion# | ||
+ | |||
+ | After creating a repository on your subversion-server, | ||
Subversion is a powerful and useful tool, and it's worth taking the time to learn about it if you expect to be doing complex customization of VuFind. | Subversion is a powerful and useful tool, and it's worth taking the time to learn about it if you expect to be doing complex customization of VuFind. | ||
Line 46: | Line 48: | ||
To get started, there two possible approaches: | To get started, there two possible approaches: | ||
+ | |||
+ | |||
+ | |||
+ | |||
==== Option A: Rely on Subversion ===== | ==== Option A: Rely on Subversion ===== | ||
Line 54: | Line 60: | ||
* 4.) Download the version of VuFind you wish to upgrade to into the “vendor” directory. | * 4.) Download the version of VuFind you wish to upgrade to into the “vendor” directory. | ||
* 5.) Merge “vendor” into “trunk.” | * 5.) Merge “vendor” into “trunk.” | ||
+ | |||
+ | Sample commands to upgrade VuFind 1.0 to current trunk (assumes that you start out in an appropriate SVN working directory -- note that this working directory should be from YOUR OWN Subversion repository, not the public VuFind one): | ||
+ | |||
+ | < | ||
+ | # Initialize vendor directory: | ||
+ | svn export https:// | ||
+ | svn add vendor | ||
+ | svn commit -m" | ||
+ | |||
+ | # Branch to trunk: | ||
+ | svn copy vendor trunk | ||
+ | svn commit -m" | ||
+ | |||
+ | # Copy your own files and update the trunk -- note that this cp command is an example | ||
+ | # but isn't really the best way to do this (it will pull in unwanted things like the | ||
+ | # Solr index and cache directories -- you should be more selective). | ||
+ | cp -r / | ||
+ | svn add --force --depth infinity trunk | ||
+ | svn commit -m" | ||
+ | |||
+ | # Load the latest version of VuFind: | ||
+ | svn export --force https:// | ||
+ | svn add --force --depth infinity vendor | ||
+ | svn commit -m" | ||
+ | |||
+ | # Merge new changes into trunk (note that if this is not a fresh repository, you may | ||
+ | # need to replace " | ||
+ | svn merge vendor@1 vendor@HEAD trunk | ||
+ | svn commit -m" | ||
+ | </ | ||
The problem is that step 5 may or may not be difficult, depending on how drastic your changes have been and how many versions of VuFind you are upgrading through. | The problem is that step 5 may or may not be difficult, depending on how drastic your changes have been and how many versions of VuFind you are upgrading through. | ||
Line 69: | Line 105: | ||
Regardless of which approach you take, once you are done, you are all set to begin using the [[subversion# | Regardless of which approach you take, once you are done, you are all set to begin using the [[subversion# | ||
+ | |||
+ | ===== Using Git ===== | ||
+ | |||
+ | Some developers prefer [[http:// | ||
---- struct data ---- | ---- struct data ---- | ||
---- | ---- | ||
legacy/vufind_1.x_developer_manual/subversion.txt · Last modified: 2018/12/19 15:00 by demiankatz