2,037
edits
Changes
From Gramps
→Stable version
The second method requires that svn be installed on your system (Debian/Ubuntu: <code>apt-get install subversion</code>; Fedora: <code>yum install subversion</code>).
With the SVN method, type the following in the command lineif you '''don't have a sourceforge account''': <code> svn co <nowiki>http://svn.code.sf.net/p/gramps/code/branches/maintenance/gramps</nowiki>{{stable_branch}} gramps{{stable_branch}}</code> You should see the downloading progress reported in your terminal. If you have a sourceforge account, use https instead: <code>
svn co <nowiki>https://svn.code.sf.net/p/gramps/code/branches/maintenance/gramps</nowiki>{{stable_branch}} gramps{{stable_branch}}</code>
You will in this case be requested for your root keyring password which will store your sourceforge credentials, and next your password. If the user on your PC is not the same one as on sourceforge, leave password empty and press enter, you will then receive the option to enter a username first, and then the sourceforge password for that username.
<code>
</code>
To commit your changes, you need to have checked out the gramps code with https, and have commit access to the Gramps repository (the Gramps admin can give you this, [[Contact|Brian Matherly or Benny Malengier]]). Commit happens if execute:
<code>
</code>
Since uploading is a potentially dangerous operation, you have to explicitly most people do not obtain write access to the SVN repository from . In this case, create a patch, and commit this on the [[Contact|Brian Matherly or Benny Malengier]http://bugs.gramps-project.org ticket tracker].You can do this in the top gramps directory as follows: <code> svn diff > mychanges.patch</code> A developer can apply this patch then with the command: <code> patch -p0 < mychanges.patch</code>
== Unstable development: "trunk" ==
