8 | | {{{abc}}} |
| 10 | * Local branch copy (for developers) |
| 11 | * Create local working directory where the local copy of branch <feature_name> is placed, we recommend: \\ mkdir -p ~/palm/branches \\ The directory branches is on the same level as the directory current_version, where the official PALM releases/revisions (trunk) should be located |
| 12 | * You can browse your branch under https://palm.muk.uni-hannover.de/trac/browser/palm/branches |
| 13 | |
| 14 | == (2 a) Checkout of local branch copy == |
| 15 | |
| 16 | * {{{cd $HOME/palm/branches/ }}} |
| 17 | * {{{ svn checkout --username <your PALM username> https://palm.muk.uni-hannover.de/svn/palm/branches/<feature_name>}}} |
| 18 | |
| 19 | == (2 b) Update of local branch copy == |
| 20 | |
| 21 | If the local branch copy already exists, and you would like to update it with a newer svn revision of this branch: |
| 22 | |
| 23 | * {{{cd $HOME/palm/branches/}}} |
| 24 | * {{{svn update <feature_name>}}} |
| 25 | |
| 26 | You can also update/downdate to or checkout a specific revision: |
| 27 | |
| 28 | * {{{svn update -r<revision number> <feature_name>}}} |
| 29 | * {{{svn checkout -r<revision number> --username ... }}} |
| 30 | |
| 31 | == (3) Code development in local ... == |
| 32 | |
| 33 | * __...'''svn''' branch copy__ \\ Versioning happens when commiting to the svn repository branch. With every commit, the PALM revision number is incremented. |
| 34 | * __...'''git''' branch copy__ \\ To avoid too numerous commits to the svn repository branch, local versioning could be done using git (→ follow steps on next slide) |
| 35 | |
| 36 | __'''NOTE'''__: As you know, in order to compile and run PALM, the PATH and PALM_BIN variables need to be set in your shell environment (e.g. .profile or .bashrc) as in this example: |
| 37 | |
| 38 | |
| 39 | |
| 40 | |