mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

document the software upgrade process minimally

Browse source
This commit is contained in:
https://id.koumbit.net/anarcat 2015-06-03 14:24:28 +00:00 • committed by admin
parent 5fd61878f5
commit 2d8d70d9d1
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
doc/upgrades.mdwn
View file

@ -1,3 +1,15 @@
[[!toc levels=2]]
# Software upgrades
Upgrading the code base of git-annex will be done differently depending on your [[install]] method. For most distribution-based packages, it is handled by the package management software.
For the standalone distribution, the [[git-annex-webapp]](1) will ask the user for confirmation when it detects a new version. Once that is confirmed, or if `annex.autoupgrade` is enabled (see the [[git-annex]](1) manpage) the assistant will start the upgrade. The upgrade process is fairly simple: the assistant will move the `git-annex.linux` directory out of the way and replace it with the new version, then re-execute itself. It therefore needs write access to the parent directory of the `git-annex.linux` directory.
Note that "upgrading" from a distribution-based package to the [[install/Linux_standalone/]] version may cause weird problems, as an unexpected version of git-annex (e.g. the old one from packages) may be ran, see [[bugs/git-annex-shell_doesn__39__t_work_as_expected/]] for a full discussion.
# Repository upgrades
Occasionally improvements are made to how git-annex stores its data, Occasionally improvements are made to how git-annex stores its data,
that require an upgrade process to convert repositories made with an older that require an upgrade process to convert repositories made with an older
version to be used by a newer version. It's annoying, it should happen version to be used by a newer version. It's annoying, it should happen