Difference between revisions of "Development"
(New page: We've no intention of releasing development, or testing versions. alas we have a stable development repository available. Using it is not meant for the faint of heart, we (by that I mean H...) |
|||
| Line 6: | Line 6: | ||
=Command Line= | =Command Line= | ||
| + | |||
| + | Command line svn is simple, if you're in linux, simply install/compile a package named subversion, and for most other OS', just get a copy from the svn website. The following code should allow most of you to check out the public repository | ||
| + | |||
| + | svn co http://www.svn.kids.platinumarts.net/32pas32 32pas32 | ||
| + | |||
| + | within that directory, you'll see a few other directories, a musicpack (which is mainly used for testing), sandbox "lite" (our attempt at a 100% free content version, no charge doesn't necessarily equal free), and the trunk (main branch), so some may prefer to use the following command to just get the main branch. | ||
| + | |||
| + | svn co http://www.svn.kids.platinumarts.net/32pas32 32pas32/trunk | ||
| + | |||
| + | to update it in the future, just change the directory to 32pas32, or in whichever directory you did the checkout out in, and type the following command | ||
| + | |||
| + | svn update | ||
| + | |||
| + | if you feel up to doing regression testing, you can append a -r(revision) to checkout a specific revision (eg, svn update -r389) | ||
=Gui Interfaces= | =Gui Interfaces= | ||
| + | |||
| + | A well designed GUI can ease the effort that may other wise be required to commit changes, access the repository, do diff (differences between two versions of a file, also called a patch). GUIs also take a bit of time getting used to, as they often have different and confusing ways of defining a repository and checking it out | ||
==esvn== | ==esvn== | ||
==Tortoise SVN== | ==Tortoise SVN== | ||
Revision as of 11:09, 13 June 2008
We've no intention of releasing development, or testing versions. alas we have a stable development repository available. Using it is not meant for the faint of heart, we (by that I mean Hirato) may occasionally break something.
Obtaining development versions is useful for testing, and it allows users (like yourself) to test out that latest and greatest of the feature set.
On a side note, we use SVN for our development repository needs.
Command Line
Command line svn is simple, if you're in linux, simply install/compile a package named subversion, and for most other OS', just get a copy from the svn website. The following code should allow most of you to check out the public repository
svn co http://www.svn.kids.platinumarts.net/32pas32 32pas32
within that directory, you'll see a few other directories, a musicpack (which is mainly used for testing), sandbox "lite" (our attempt at a 100% free content version, no charge doesn't necessarily equal free), and the trunk (main branch), so some may prefer to use the following command to just get the main branch.
svn co http://www.svn.kids.platinumarts.net/32pas32 32pas32/trunk
to update it in the future, just change the directory to 32pas32, or in whichever directory you did the checkout out in, and type the following command
svn update
if you feel up to doing regression testing, you can append a -r(revision) to checkout a specific revision (eg, svn update -r389)
Gui Interfaces
A well designed GUI can ease the effort that may other wise be required to commit changes, access the repository, do diff (differences between two versions of a file, also called a patch). GUIs also take a bit of time getting used to, as they often have different and confusing ways of defining a repository and checking it out
