You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Jelle van der Waa c7167042ca
Update cargo dependencies
1 year ago
doc Fix typo in "pn" in man page 1 year ago
src Sort the reverse dependencies so output is predictable 1 year ago
tests Add a test for multiple inputs 1 year ago
.gitignore Add a man page 1 year ago
.gitlab-ci.yml Add cargo audit lint step 1 year ago
Cargo.lock Update cargo dependencies 1 year ago
Cargo.toml Update cargo dependencies 1 year ago
LICENSE Add MIT License file 2 years ago
Makefile Add a separate completion generation 1 year ago Update README with opencolorio1 as example pkg 1 year ago

Arch Linux Rebuild Order Tool

A CLI tool to determine the rebuild order of provided package(s).


To show the rebuild order of opencolorio1

cargo run opencolorio1


  • Generate a list of packages to rebuild in order for given package(s).
  • Generate the build order within one second.


Arch-rebuild-order uses the local syncdb to build a hashmap, mapping packages to their reverse (make) dependencies. The provided pkgnames are looked up in the syncdb and a hashmap is built of the package provides and the pkgname called provides_map. The pkgnames and provides are added to the to_visit list and this then starts the iteration over every entry in the list. During each iteration, the real package name is resolved if the provided package comes from provides using the provides_map, a graph node is created for the entry. For all reverse (make) dependencies of the entry, the dependency is added to the to_visit list, a new graph node is created and added as an edge of the pkg node. This repeats until the to_visit list is empty.

DOT output

Arch-rebuild-order can generate a DOT file of the rebuild order for a given package.

cargo run -- -d opencolorio1
dot -Tpng > opencolorio.png


  • testing and community-testing repositories are not included.
  • Arch-rebuild-order expects an up-to-date syncdb and does not provide warning if it is not.


Shell completions can be created with cargo run --bin completions in a directory specified by the env variable OUT_DIR.