Update within the same version using git » History » Version 1
Anchi Cheng, 05/25/2017 05:05 PM
1 | 1 | Anchi Cheng | h1. Update within the same version using git |
---|---|---|---|
2 | |||
3 | From time to time, we discover critical bugs that users are encouraged to update within the branch (x.x version) that they have checked out. Here is how to update when these situation arrives. |
||
4 | |||
5 | h2. You still have the git clone of the whole myami superpackage (May still be in /tmp/myami if you used autoinstaller): |
||
6 | |||
7 | # Go to the myami directory |
||
8 | # Confirm that this checkout working sandbox is the branch you want: |
||
9 | ** Linux |
||
10 | <pre> |
||
11 | git status |
||
12 | </pre> |
||
13 | # update the clone |
||
14 | ** Linux |
||
15 | <pre> |
||
16 | git pull |
||
17 | </pre> |
||
18 | ** Windows |
||
19 | <pre> |
||
20 | RIght-click on the myami top folder icon to select GitBash Here, and then type in there: |
||
21 | git pull |
||
22 | </pre> |
||
23 | You should see what has been changed by the update |
||
24 | # For the each of the *python subpackage* that changes are made, redo the python installation with the same command you used originally. For example, if changes were made in leginon subpackage, you would install leginon by |
||
25 | ** Linux |
||
26 | <pre> |
||
27 | cd /_your_myami_git_clone_/leginon |
||
28 | python setup.py install |
||
29 | </pre> |
||
30 | ** Windows from command line |
||
31 | <pre> |
||
32 | cd \_your_myami_git_clone_\leginon |
||
33 | C:\Python25\python.exe setup.py install |
||
34 | </pre> |
||
35 | # For changes made in myamiweb, you should just copy individual files involved to your webserver at the relevant locations. You may also replace the whole myamiweb directory over, but you will then need to cp config.php from the old copy into the new one. |