|
|
| (62 intermediate revisions by 19 users not shown) |
| Line 1: |
Line 1: |
| − | Now that the gnucash repository is using svn for version control (since 2005-11-04), the need for a quick tutorial on how to get the sources might be in order. There was some introduction about SVN in an [http://lists.gnucash.org/pipermail/gnucash-devel/2005-October/014333.html e-mail] on gnucash-devel:
| + | =This page is obsolete= |
| | | | |
| − | The excellent "[http://svnbook.red-bean.com/ Version Control with Subversion] is a very good resource
| + | GnuCash has switched to git to manage its source code. Please refer to the [[git]] page if you want to check out the source code. Do not start from svn anymore. |
| − | for information about subversion.
| |
| − | | |
| − | Specifically, [http://svnbook.red-bean.com/en/1.1/ch03.html Chapter 3. Guided Tour]
| |
| − | and [http://svnbook.red-bean.com/en/1.1/apa.html Appendix A. Subversion for CVS Users] are relevant.
| |
| − | | |
| − | The command-line client `<tt>svn</tt>` has a nice integrated help system; `<tt>svn help</tt>`
| |
| − | will provide the top-level command list, and `<tt>svn help <command></tt>` detailed
| |
| − | help for the specific command.
| |
| − | | |
| − | The bottom line is that getting the source via svn isn't altogether different from getting it using cvs.
| |
| − | | |
| − | ===CVS to SVN cross reference===
| |
| − | {| cellpadding="2"
| |
| − | |-
| |
| − | | cvs checkout
| |
| − | | ->
| |
| − | | svn checkout
| |
| − | |-
| |
| − | | cvs commit
| |
| − | | ->
| |
| − | | svn commit
| |
| − | |-
| |
| − | | cvs status
| |
| − | | ->
| |
| − | | svn status [...but one that's actually useful :)]
| |
| − | |-
| |
| − | | cvs log
| |
| − | | ->
| |
| − | | svn log
| |
| − | |-
| |
| − | | cvs annotate
| |
| − | | ->
| |
| − | | svn blame
| |
| − | |-
| |
| − | | cvs diff
| |
| − | | ->
| |
| − | | svn diff
| |
| − | |-
| |
| − | | cvs update
| |
| − | | ->
| |
| − | | svn update, svn switch
| |
| − | |-
| |
| − | | cvs update -C
| |
| − | | ->
| |
| − | | svn revert
| |
| − | |-
| |
| − | | cvs update -j [...]
| |
| − | | ->
| |
| − | | svn merge
| |
| − | |-
| |
| − | | <nowiki> ---- </nowiki>
| |
| − | | ->
| |
| − | | svn resolved [conflicting merges must be explicitly resolved]
| |
| − | |-
| |
| − | | cvs add
| |
| − | | ->
| |
| − | | svn add, svn mkdir
| |
| − | |-
| |
| − | | cvs remove
| |
| − | | ->
| |
| − | | svn delete
| |
| − | |-
| |
| − | |<nowiki> ---- </nowiki>
| |
| − | | ->
| |
| − | | svn move
| |
| − | |-
| |
| − | | cvs [r]tag [-b]
| |
| − | | ->
| |
| − | | svn copy
| |
| − | |}
| |
| − | | |
| − | ===URLs===
| |
| − | The various base URLs look like:
| |
| − | | |
| − | anonymous: <nowiki>http://svn.gnucash.org/repo/gnucash/trunk</nowiki>
| |
| − | developer: svn+ssh://username@svn.gnucash.org/repo/gnucash/trunk
| |
| − | trac: http://svn.gnucash.org/trac
| |
| − | | |
| − | ===Common Commands===
| |
| − | To get what used to be CVS HEAD (and now includes what used to be gnucash-gnome2-dev), you will need to get the svn TRUNK:
| |
| − | | |
| − | svn checkout <nowiki>http://svn.gnucash.org/repo/gnucash/trunk</nowiki> gnucash
| |
| − | | |
| − | The argument "gnucash" above can be whatever you want your local directory to be called, and is optional. If you leave it out, you'll have a directory called "trunk" created containing all the source code.
| |
| − | | |
| − | If you want the latest 1.8.x code, you'd need to pull from the 1.8 branch, as follows:
| |
| − | | |
| − | svn checkout <nowiki>http://svn.gnucash.org/repo/gnucash/branches/1.8</nowiki> gnucash-1.8
| |
| − | | |
| − | And if you want the released code for a specific release (or tag), you'd use:
| |
| − | | |
| − | svn checkout <nowiki>http://svn.gnucash.org/repo/gnucash/tags/1.8.12</nowiki> gnucash-1.8.12
| |
| − | | |
| − | And to update, just cd into the directory containing the sources you want updated and execute a simple
| |
| − | | |
| − | svn update
| |
| − | | |
| − | Please examine the README.svn file for notes on compiling gnucash, and the HACKING file for notes on hacking the code.
| |
| − | | |
| − | Enjoy!
| |
