User:Pedrobeltrao/Notebook/Structural analysis of phosphorylation sites/Code
From OpenWetWare
(→SVN usage) |
(→SVN usage) |
||
| Line 33: | Line 33: | ||
# Update again | # Update again | ||
# Submit (check in) your change to the server | # Submit (check in) your change to the server | ||
| + | |||
| + | 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: | Example: | ||
Revision as of 14:18, 26 September 2009
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:
cd phospho3d svn update ...make your change; e.g. add new file myscript.py... svn add myscript.py svn status ...check what has changed locally... svn ci -m 'your checkin message'
By default, svn commands operate on the local folder and all sub-folders. You can limit them to certain files:
| |


