User:Pedrobeltrao/Notebook/Structural analysis of phosphorylation sites/Code: Difference between revisions
(→Access) |
|||
(3 intermediate revisions by the same user not shown) | |||
Line 34: | Line 34: | ||
# Submit (check in) your change to the server | # Submit (check in) your change to the server | ||
Example: | There are many graphical front-ends to subversion and most programming environments integrate some subversion support. But even without any GUI candy, you only need to remember 3 or 4 svn commands to work on the code. These are: | ||
* svn add -- add a new file/files into version control | |||
* svn update -- merge changes from the server into your local copy | |||
* svn checkin (short: svn ci) -- submit changes to the server | |||
* svn status -- list local changes (option -u lists remote changes too) | |||
====Example:==== | |||
<code> | <code> | ||
cd phospho3d | cd phospho3d | ||
svn update | svn update | ||
...make your change... | |||
...make your change; e.g. add new file myscript.py... | |||
svn add myscript.py | svn add myscript.py | ||
svn status | svn status | ||
...check what has changed locally... | ...check what has changed locally... | ||
svn update | |||
svn ci -m 'your checkin message' | svn ci -m 'your checkin message' | ||
</code> | </code> | ||
Allways update your local copy to the latest state **directly before** checking in any change! | |||
By default, svn commands operate on the local folder and all sub-folders. You can limit them to certain files: | By default, svn commands operate on the local folder and all sub-folders. You can limit them to certain files: | ||
<code> | <code> |
Latest revision as of 11:23, 26 September 2009
Structural analysis of phosphorylation sites | |
CodeWe are going to use Perl (Pedro) and Python (Raik). The Python code builds on the Biskit library. Our scripts are available through Google Code: Access1. Install a subversion (svn) client 2. Then check out the latest version of the code:
3. Before running python scripts, you also need to install the Biskit library
SVN usageAfter the initial checkout, the basic principle is always:
There are many graphical front-ends to subversion and most programming environments integrate some subversion support. But even without any GUI candy, you only need to remember 3 or 4 svn commands to work on the code. These are:
Example:
Allways update your local copy to the latest state **directly before** checking in any change!
By default, svn commands operate on the local folder and all sub-folders. You can limit them to certain files:
|