| 131 | | == [=#update]Installation of new / other revisions, revision update == |
| 132 | | |
| 133 | | All code revisions are documented under [wiki:doc/tec/changelog]. The PALM group announces major code revisions via the PALM mailing list. You will be automatically set on the list by creating an account using the [[//trac/register|register form]].\\\\ |
| 134 | | Generally, there are two ways of installing new / other versions. You can install a version from the [wiki:doc/tec/releasenotes list of available PALM releases] or you can update your current installation with the newest developer revision of PALM.\\\\ |
| 135 | | If you have previously checked out the PALM developer revison by using |
| 136 | | {{{ |
| 137 | | svn checkout ...../palm/trunk trunk |
| 138 | | }}} |
| 139 | | you can easily make an update to the newest revision by |
| 140 | | {{{ |
| 141 | | cd ~/palm/current_version |
| 142 | | svn update trunk |
| 143 | | }}} |
| 144 | | This updates all files in the working copy in folder {{{trunk}}} (which is your working copy of the PALM repository). The update may fail due the '''subversion''' rules, if you have modified the contents of trunk. In case of any conflicts with the repository, please refer to the '''subversion''' documentation on how to remove them. In order to avoid such conflicts, modifications of the default PALM code should be omitted and be restricted to the user-interface only (see [../app/userint here]), except you are a PALM developer.\\\\ |
| 145 | | Alternatively, you can install new or other releases in a different directory, eg. |
| 146 | | {{{ |
| 147 | | mkdir ~/palm/release-4.0 |
| 148 | | cd ~/palm/release-4.0 |
| 149 | | svn checkout --username <your username> https://palm.muk.uni-hannover.de/svn/palm/tags/release-4.0 trunk |
| 150 | | }}} |
| 151 | | However, this requires to carry out again the complete installation process described above. So far, different versions of PALM cannot be used at the same time. The PALM releases from {{{palm/tags}}} never have to be updated with "{{{svn update}}}", since these versions are frozen! \\\\ |
| 152 | | |
| 153 | | The compiled PALM code and helper routines must then be updated via |
| 154 | | {{{ |
| 155 | | palmbuild -c default |
| 156 | | }}} |
| 157 | | or for any other configuration files that you are using.\\\\ |
| 158 | | You can use '''subversion''' for code comparison between the different revisions. Also, modified code can be committed to the repository, but this is restricted to PALM developers.\\\\ |
| 159 | | |
| 160 | | If you want to recompile PALM via {{{palmbuild}}} after you have modified the configuration file (e.g. if you changed compiler options or switched to other libraries), you need to apply the {{{touch}}} command on all source files in advance: |
| 161 | | {{{ |
| 162 | | touch trunk/SOURCE/* |
| 163 | | }}} |
| 164 | | because otherwise the {{{make}}} mechanism will not detect any source file that needs to be compiled. As an alternative, instead of ''touching'' the files, you may delete the {{{MAKE_DEPOSITORY}}} folder before calling {{{palmbuild}}}, but then the complete code will be re-compiled. |
| 165 | | |
| 166 | | As a last step, a suitable test run should be carried out. It should be carefully examined whether and how the results created by the new revision differ from those of the old version. Possible discrepancies which go beyond the ones announced in the [wiki:doc/tec/changelog PALM change log] should be communicated as soon as possible via our [/newticket ticket system].\\\\ |
| 167 | | |
| 168 | | |
