ALR-WITH(1) | Alire manual | ALR-WITH(1) |
alr-with - Manage release dependencies
alr with [options] [{ [--del] <crate>[versions]... | --from <gpr_file>... | <crate>[versions] --use <path> [--commit REF] [--branch NAME]} ] | --solve | --tree | --versions
Inspect and manage dependencies.
Run without arguments prints current dependencies. Use --solve to print the solution in use for these dependencies.
Dependencies are added by giving their name, and removed by using the --del flag. Dependencies cannot be simultaneously added and removed in a single invocation.
When a single crate name is accompanied by an --use PATH|URL argument, the crate is always fulfilled for any required version by the sources found at the given target. An optional reference can be specified with --commit; the pin will be frozen at the commit currently matching the reference. Alternatively, a branch to track can be specified with --branch. Use `alr update` to refresh the tracking pin contents.
The project file given with --from will be scanned looking for comments that contain the sequence 'alr with'. These will be processed individually as if they had been given in the command line, starting with no dependencies. That is, only dependencies given in the GPR file will be preserved. Example of GPR file contents: with "libhello"; -- alr with libhello Version selection syntax (global policy applies within the allowed version subsets):
crate Newest/oldest version
crate=version Exact version
crate^version Major-compatible version
crate~version Minor-compatible version
alr(1), alr-get(1), alr-index(1), alr-init(1), alr-pin(1), alr-search(1), alr-show(1), alr-update(1), gprbuild(1)
Generated with generate-man from Alire execution
August 3, 2022 | Alire 1.2 |