Changes between Version 1 and Version 2 of GettingStarted


Ignore:
Timestamp:
01/30/09 13:59:45 (5 years ago)
Author:
admin
Comment:

Updated subversion path to https://nanohub.org/tools/spice3f4/svn/trunk

Legend:

Unmodified
Added
Removed
Modified
  • GettingStarted

    v1 v2  
    99Once Subversion is installed, you download Spice3F4 as follows: 
    1010{{{ 
    11 % svn checkout https://repo.nanohub.org/svn/app-spice3f4/trunk app-spice3f4 
     11% svn checkout https://nanohub.org/tools/spice3f4/svn/trunk spice3f4 
    1212}}} 
    1313 
    14 The {{{checkout}}} command makes a local copy of the entire Spice3F4 source tree into your current working directory as a subdirectory called {{{app-spice3f4}}}.  By requesting {{{.../app-spice3f4/trunk}}}, you get the main development trunk, which should have the latest stable code. 
     14The {{{checkout}}} command makes a local copy of the entire Spice3F4 source tree into your current working directory as a subdirectory called {{{app-spice3f4}}}.  By requesting {{{.../spice3f4/svn/trunk}}}, you get the main development trunk, which should have the latest stable code. 
    1515 
    1616== Making Changes == 
     
    1818Once you've downloaded the code, you can make whatever changes you like.  For example, you might edit a file to fix a bug or add some code.  To make your changes permanent, you must {{{commit}} them to the repository as follows: 
    1919{{{ 
    20 % cd app-spice3f4 
     20% cd spice3f4 
    2121% svn commit --message "fixed my first bug!" 
    2222}}} 
    2323You don't have to include the optional {{{--message}}} argument.  If you just say {{{svn commit}}}, Subversion will prompt you for comments in your favorite editor, and you can type much more. 
    2424 
    25 It's best to commit at the top of the source tree--that's why we said "{{{cd app-spice3f4}}}" in the example above.  When you commit at the top of the tree, Subversion will search everything below, find all files that have changed, and commit them all at once.  Committing a change makes it permanent.  Once committed, other developers will see the change.  If for some reason, you want to throw away your changes and start fresh, you can simply remove your source tree and check it out all over again.  Or, you may want to remove just a few files that you've modified, and then {{{update}}} (as we'll see below) to replace the missing files with their previous version. 
     25It's best to commit at the top of the source tree--that's why we said "{{{cd spice3f4}}}" in the example above.  When you commit at the top of the tree, Subversion will search everything below, find all files that have changed, and commit them all at once.  Committing a change makes it permanent.  Once committed, other developers will see the change.  If for some reason, you want to throw away your changes and start fresh, you can simply remove your source tree and check it out all over again.  Or, you may want to remove just a few files that you've modified, and then {{{update}}} (as we'll see below) to replace the missing files with their previous version. 
    2626 
    2727From time to time, you and another developer will modify the same file at the same time.  Suppose the other developer checks in his changes first.  When you try to commit, you'll get an error saying that your file is out-of-date.  In that case, you need to {{{update}}} before committing.  You can do that as follows: 
    2828{{{ 
    29 % cd app-spice3f4 
     29% cd spice3f4 
    3030% svn update 
    3131}}} 
    32 It's best to update at the top of the source tree--just like commit.  That's why we said "{{{cd app-spice3f4}}}" in the example above.  When you update at the top of the tree, Subversion will search everything below, adding any new files, replacing any missing files, and integrating changes made by other developers.  Once all files are properly updated, you can commit your changes again, and this time, it will work. 
     32It's best to update at the top of the source tree--just like commit.  That's why we said "{{{cd spice3f4}}}" in the example above.  When you update at the top of the tree, Subversion will search everything below, adding any new files, replacing any missing files, and integrating changes made by other developers.  Once all files are properly updated, you can commit your changes again, and this time, it will work.