|
|
| (55 intermediate revisions by 17 users not shown) |
| Line 1: |
Line 1: |
| − | =Repository URLs= | + | =This page is obsolete= |
| − | The various base URLs look like:
| |
| | | | |
| − | anonymous: <nowiki>http://svn.gnucash.org/repo/gnucash/trunk</nowiki>
| + | 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. |
| − | developer: svn+ssh://username@svn.gnucash.org/repo/gnucash/trunk
| |
| − | trac: http://svn.gnucash.org/trac
| |
| − | | |
| − | Note: if you are having problems with the http:// anonymous access, make sure your subversion is compiled with [http://www.webdav.org/neon/ neon] support.
| |
| − | | |
| − | =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
| |
| − | | |
| − | You probably want to read on on the [[Building]] page.
| |
| − | | |
| − | = SVN tutorial =
| |
| − | | |
| − | 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:
| |
| − | | |
| − | The excellent "[http://svnbook.red-bean.com/ Version Control with Subversion] is a very good resource 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" cellspacing="0" border="1"
| |
| − | | *CVS command*
| |
| − | | *SVN command*
| |
| − | | *notes*
| |
| − | |-
| |
| − | | cvs checkout
| |
| − | | svn checkout
| |
| − | |
| |
| − | |-
| |
| − | | cvs commit
| |
| − | | svn commit
| |
| − | |
| |
| − | |-
| |
| − | | cvs status
| |
| − | | svn status
| |
| − | | ...but the svn one is actually useful :)
| |
| − | |-
| |
| − | | cvs log
| |
| − | | svn log
| |
| − | |
| |
| − | |-
| |
| − | | cvs annotate
| |
| − | | svn blame
| |
| − | |
| |
| − | |-
| |
| − | | cvs diff
| |
| − | | svn diff
| |
| − | |
| |
| − | |-
| |
| − | | cvs diff -D 2006-01-01
| |
| − | | svn diff -r {2006-01-01}:HEAD
| |
| − | |
| |
| − | |-
| |
| − | | 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
| |
| − | |
| |
| − | |}
| |
| − | | |
| − | | |
| − | Enjoy!
| |
| − | | |
| − | =SVN write access=
| |
| − | | |
| − | FAQ: Is it possible to get SVN write access?
| |
| − | | |
| − | A: In principle yes, but we are quite conservative with giving out new SVN write accounts. For occasional changes people are encouraged to submit patches. We do add people as developers if then stick around, supply lots of patches, become highly involved in the project, hang out on IRC, and generally show some level of clue and prove some level of trust. But in the meantime, patches in email are the suggested route, as has been stated at other places. --[[User:Cstim|Cstim]] 08:00, 8 January 2006 (EST)
| |
