`xbstrap update`

[no92]

[avdgrinten]

What's the benefit of this command compared to xbstrap install --update?

[no92]

Rebased the PR on master. As discussed on Discord, the typical use-case is updating some or all installed packages to avoid partial upgrades, as it happens with individual package updates by means of xbstrap install -u or a git pull.

The interface looks like this:

$ xbstrap update --help
usage: xbstrap update [-h] [-n] [-c] [-u] [-p] [--recursive] [--paranoid] [--reset] [--hard-reset] [--only-wanted] [--keep-going]
                      [--progress-file PROGRESS_FILE] [--all] [--deps-of DEPS_OF] [-i] [-v]
                      [packages ...]

Update packages to their newest version. When --all is used, --installed is implied.

positional arguments:
  packages

options:
  -h, --help            show this help message and exit
  -n, --dry-run         compute a plan but do not execute it
  -c, --check           skip packages that are already built/installed/etc.
  -u, --update          check for package updates
  -p, --pull            pull packages instead of building from source
  --recursive           when updating: also update requirements
  --paranoid            also consider unlikely updates (e.g., changes of git tags)
  --reset               reset repository state; risks loss of local commits!
  --hard-reset          clean and reset repository state; risks loss of local changes and commits!
  --only-wanted         fail steps that are not explicitly wanted
  --keep-going          continue running even if some build steps fail
  --progress-file PROGRESS_FILE
                        file that receives machine-ready progress notifications
  --all
  --deps-of DEPS_OF
  -i, --installed       only select packages that are already installed
  -v, --verbose         print every version check performed