alibuild 1.17.31__py3-none-any.whl → 1.17.33__py3-none-any.whl

{alibuild-1.17.31.dist-info → alibuild-1.17.33.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: alibuild
-Version: 1.17.31
+Version: 1.17.33
 Summary: ALICE Build Tool
 Home-page: https://alisw.github.io/alibuild
 Author: Giulio Eulisse
@@ -56,14 +56,22 @@ Pre-requisites
 If you are using aliBuild directly from git clone, you should make sure
 you have the dependencies installed. The easiest way to do this is to run::
 
+    # Optional, make a venv so the dependencies are not installed globally
+    python -m venv .venv
+    source .venv/bin/activate
     pip install -e .
 
 
-For developers
-==============
+Contributing
+============
+
 
 If you want to contribute to aliBuild, you can run the tests with::
 
+    # Optional, make a venv so the dependencies are not installed globally
+    python -m venv .venv
+    source .venv/bin/activate
+
     pip install -e .[test] # Only needed once
     tox
 
@@ -77,6 +85,13 @@ You can also run only the unit tests (it's a lot faster than the full suite) wit
 
 To run the documentation locally, you can use::
 
+    # Optional, make a venv so the dependencies are not installed globally
+    python -m venv .venv
+    source .venv/bin/activate
+
+    # Install dependencies for the docs, check pyproject.toml for more info
     pip install -e .[docs]
+
+    # Run the docs
     cd docs
     mkdocs serve

{alibuild-1.17.31.dist-info → alibuild-1.17.33.dist-info}/RECORD

@@ -1,15 +1,15 @@
-alibuild-1.17.31.data/scripts/aliBuild,sha256=5g-apCjhc9cvtFvKSP0yr6IJtChNvtTAP-BtPL-91M8,4307
-alibuild-1.17.31.data/scripts/aliDeps,sha256=fhfPB2NpuLj8bZZPUjJW2e4VxA8ZkHlp5q76xAOzufI,219
-alibuild-1.17.31.data/scripts/aliDoctor,sha256=gQwLcNGAm7_QF7FFCtmtFXEoroKsRonNMA7UP4DS1y4,221
-alibuild-1.17.31.data/scripts/alienv,sha256=8QihJOzKue4oeuIM31MsoX8Fw7FNZ4zY7wyK6UYtgTE,12568
-alibuild-1.17.31.data/scripts/pb,sha256=LfkIUyX3xXxmaGSdtAbA-dS1Y1eEShEHpmto1tIEga0,211
-alibuild-1.17.31.dist-info/licenses/LICENSE.md,sha256=WJ7YI-moTFb-uVrFjnzzhGJrnL9P2iqQe8NuED3hutI,35141
+alibuild-1.17.33.data/scripts/aliBuild,sha256=5g-apCjhc9cvtFvKSP0yr6IJtChNvtTAP-BtPL-91M8,4307
+alibuild-1.17.33.data/scripts/aliDeps,sha256=fhfPB2NpuLj8bZZPUjJW2e4VxA8ZkHlp5q76xAOzufI,219
+alibuild-1.17.33.data/scripts/aliDoctor,sha256=gQwLcNGAm7_QF7FFCtmtFXEoroKsRonNMA7UP4DS1y4,221
+alibuild-1.17.33.data/scripts/alienv,sha256=8QihJOzKue4oeuIM31MsoX8Fw7FNZ4zY7wyK6UYtgTE,12568
+alibuild-1.17.33.data/scripts/pb,sha256=LfkIUyX3xXxmaGSdtAbA-dS1Y1eEShEHpmto1tIEga0,211
+alibuild-1.17.33.dist-info/licenses/LICENSE.md,sha256=WJ7YI-moTFb-uVrFjnzzhGJrnL9P2iqQe8NuED3hutI,35141
 alibuild_helpers/__init__.py,sha256=ZAhyhRxOkiTA1fMzwEKACY8Eo8MdWp1MawVicFlvQWk,736
-alibuild_helpers/_version.py,sha256=TrTIouZBUnhS2cZ2YpeAFitQiBMrqfCdnZqquPAw5SU,708
+alibuild_helpers/_version.py,sha256=aocBG_OE5hC31Qts18qEBqT2J_scMmIDImpzF42ytV8,708
 alibuild_helpers/analytics.py,sha256=fuiOagDngFnodGo7upMWeY-RjTTncDRz5Kwz8zxUr9o,4579
 alibuild_helpers/args.py,sha256=T0nOOMCpJZdJkEPZENz7nOsaYIfeZ7qHfAR1Vx4-T2Y,31694
 alibuild_helpers/build.py,sha256=VJj0KwRkbPs5gCj-Ey2MWhl2NTLZWql6DGwp8AO3tTA,57055
-alibuild_helpers/build_template.sh,sha256=e7nh8ZhNH-z0LPkuETYVYlgM75EfhoCo__hn1QCIDak,13566
+alibuild_helpers/build_template.sh,sha256=yx1YEQN5tdfQNmZfsEnn-FxbzBIpvYwYRQkQLKmm8uo,14011
 alibuild_helpers/clean.py,sha256=-LeQUYDwxihzGJi4rCiuALu051T44-0cV8S6-l_lCaQ,3250
 alibuild_helpers/cmd.py,sha256=5tdxtyrHDzmdSVIA0pzxBoici1GZDS0fUStbX85r6ao,5906
 alibuild_helpers/deps.py,sha256=nHLyNqVuTUfW5bqfzCDxAaVVsklv5wHMl4FMMfTQF-8,4909
@@ -29,16 +29,15 @@ debian/control,sha256=UL8ZCLiCnNH75oVtldYPfrBO8DH7VxvjXPIdTCvXgPc,476
 debian/copyright,sha256=wOLKnTq7-L1OZZoXu-FOojSdqt2nb9aEwVqVZGAxanE,470
 debian/files,sha256=u9Y63SK26643_rgHm6lvcr4OtZKlCM-FcW4wwiJ4FMY,55
 debian/rules,sha256=V4agtbpfdaM9h7oNrgNzEShthUASwMfhgTmFvZKLNMI,131
-docs/README.md,sha256=-2EVG9RlHchf-TYJIxwZf8zSHc49ujCdTzZmWrxj4aQ,64
 docs/SUPPORT,sha256=j8Ikz-9B8OkoZwtd7WU5fc_qRQ_MWy2qjWcgsXY3XyQ,150
 docs/mkdocs.yml,sha256=FQWSVZC75WnuCs6icnSRauBgIJ4hrVut5Rt9X4zxy-w,931
 docs/docs/alice_logo.png,sha256=w8Jpk9mHdGF5sN0pO0i6PuVyI-ntDNsvbx7DChVIZQQ,65824
 docs/docs/deps.png,sha256=VY_WJOzWOm_JqAwuzFBd6C7NhrzTDDireNh739NwAow,261802
 docs/docs/index.md,sha256=pU3PRsZvV5M_W1-GEZ169ECAD4C5eQc0l2V_kN_j7yU,3571
 docs/docs/quick.md,sha256=PTKHAmt6vrEc3QbaRAS7rZICZ-LcvdqLxgaNcXo63Sw,2967
-docs/docs/reference.md,sha256=g516_jCRnFOFy1kgw4d7Bin7OH1UBT4V34JVeDf_kBA,18033
-docs/docs/troubleshooting.md,sha256=SvNT68iCVXFu3RMKjLQZrMwxBxaOSJ-QeSJe8Q3N4Oc,15440
-docs/docs/user.md,sha256=3Ys1cwNuDTBQl7zZZisChZ4mt9KrLduH1bLUHXK5Jws,18704
+docs/docs/reference.md,sha256=sBH8diOwyOFkgDsAhWexvtpuAwZaNzJaE-dplEnOXdU,18049
+docs/docs/troubleshooting.md,sha256=fcAoLyi46yxMztqbYMY-5Z4_mwLZOJW8Q3M3jEb-Zdc,15458
+docs/docs/user.md,sha256=5o150ssZnN1Tow35OWA6Gfw3PjlhJb27ip1740hasV8,20476
 docs/docs/stylesheets/extra.css,sha256=NAFcBZQe8gh2CTpJFwyv93FvblnF5RaEjtsHxtlFD-w,215
 templates/alibuild_to_please.jnj,sha256=48SfIwq55zlb5_5lu6WAHSznXE0EfUNcHmFrmzMUSns,1723
 tests/test_analytics.py,sha256=IlxATGj-MU0sTVqpi2-EKrIhyV9C48K5IZ39kWFz-Os,1942
@@ -68,7 +67,7 @@ tests/testdist/clobber-initdotsh.sh,sha256=K4L8hiEgNg0hI2WAiEA65rWU5sp-fwOYkubpV
 tests/testdist/defaults-o2.sh,sha256=IJWVMYjQYz876twos1bj-5VnPv7WTdM0X-fd09j4xxM,325
 tests/testdist/delete-etc.sh,sha256=NFMApyWMLQu3HJMsx0x8ZEveCaXbosO6XzJk8KDRJdg,63
 tests/testdist/tracking-env.sh,sha256=3cJszuzJ5dxNYvHO4ydUOWIXwmMS7wfeb-JBCDK21O4,119
-alibuild-1.17.31.dist-info/METADATA,sha256=7-XtaJpu2T0OFXaBUde9PEVc5-_1miUl3ottGQAp-9Y,2231
-alibuild-1.17.31.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-alibuild-1.17.31.dist-info/top_level.txt,sha256=WjKmc89Vn0WlbEp9a9VmhwqRkeKxjUX_6NT3T8K3Hv0,45
-alibuild-1.17.31.dist-info/RECORD,,
+alibuild-1.17.33.dist-info/METADATA,sha256=0riqP6LrOo5K2bEefvmo6XRIxzbL2K9G63MmFHvbPZI,2716
+alibuild-1.17.33.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+alibuild-1.17.33.dist-info/top_level.txt,sha256=WjKmc89Vn0WlbEp9a9VmhwqRkeKxjUX_6NT3T8K3Hv0,45
+alibuild-1.17.33.dist-info/RECORD,,

alibuild_helpers/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '1.17.31'
-__version_tuple__ = version_tuple = (1, 17, 31)
+__version__ = version = '1.17.33'
+__version_tuple__ = version_tuple = (1, 17, 33)
 
 __commit_id__ = commit_id = None

alibuild_helpers/build_template.sh

@@ -1,7 +1,18 @@
 #!/bin/bash
-
+ALIBUILD_START_TIMESTAMP=$(date +%%s)
 # Automatically generated build script
 unset DYLD_LIBRARY_PATH
+echo "aliBuild: start building $PKGNAME-$PKGVERSION-$PKGREVISION at $ALIBUILD_START_TIMESTAMP"
+
+cleanup() {
+  local exit_code=$?
+  ALIBUILD_END_TIMESTAMP=$(date +%%s)
+  ALIBUILD_DELTA_TIME=$(($ALIBUILD_END_TIMESTAMP - $ALIBUILD_START_TIMESTAMP))
+  echo "aliBuild: done building $PKGNAME-$PKGVERSION-$PKGREVISION at $ALIBUILD_START_TIMESTAMP (${ALIBUILD_DELTA_TIME} s)"
+  exit $exit_code
+}
+
+trap cleanup EXIT
 
 # Cleanup variables which should not be exposed to user code
 unset AWS_ACCESS_KEY_ID

docs/docs/reference.md

@@ -79,13 +79,16 @@ The following entries are optional in the header:
   - `source`: URL of a Git repository from which the source is downloaded.
     It's good practice to make sure that they are already patched, so that you
     can easily point to the actual sources used by the software.
+
   - `write_repo`: in case the repository URL to be used for developing is
     different from the `source`, set this key. It is used by `aliBuild init`,
     which will initialise your local repository with the `upstream` remote
     pointing at this URL instead of the one in `source`.
+
   - `tag`: git reference in the above mentioned repository which points to the
     software to be built. This can be a tag name, a branch name or a commit
     hash.
+
   - `env`: dictionary whose key-value pairs are environment variables to be set
     after the recipe is built. The values are interpreted as the contents of a
     double-quoted shell string, so you can reference other environment variables
@@ -101,6 +104,7 @@ The following entries are optional in the header:
     intended to be used to point to build products of the current recipe. If you
     need to set an environment variable for use in the recipe, use
     `export VARIABLE=value` in the recipe body.
+
   - `prepend_path`: dictionary whose key-value pairs are an environment variable
     name and a path to be prepended to it, as it happens in `LD_LIBRARY_PATH`.
     This happens only after the package declaring the `prepend_path` in question
@@ -116,9 +120,11 @@ The following entries are optional in the header:
 
     will result in prepending `$FOO_ROOT/binexec/foobar` to `$PATH`, and both
     `$FOO_ROOT/sub/lib` and `lib64` to `LD_LIBRARY_PATH`.
+
   - `append_path`: same as `prepend_path` but paths are appended rather than
     prepended. Like `append_path` and `env`, this **does not** affect the
     environment of the current recipe.
+
   - `requires`: a list of run-time dependencies for the package, *e.g.*:
 
     ```yaml
@@ -145,17 +151,20 @@ The following entries are optional in the header:
 
     will make sure that `IgProf` is only built on platforms whose name does not
     begin with `osx`.
+
   - `build_requires`: a list of build-time dependencies for the package. Like
     `requires`, these packages will be built before the current package is
     built.
 
     Packages in this list are marked specially in the dependency graph
-    produced by `aliDeps`. Other tools treat these packages differently from
+    produced by `aliBuild deps`. Other tools treat these packages differently from
     `requires`: for instance, RPMs produced for a package won't depend on its
     `build_requires`, and `alibuild-generate-module` won't pull in build
     requirements' modulefiles.
+
   - `force_rebuild`: set it to `true` to force re-running the build recipe every
     time you invoke alibuild on it.
+
   - `prefer_system_check`: a script which is used to determine whether
     or not the system equivalent of the package can be used. See also
     `prefer_system`. If the `--no-system` option is specified, this key is not
@@ -170,6 +179,7 @@ The following entries are optional in the header:
     does not match, the check is skipped and the recipe is run. Using the switch
     `--always-prefer-system` runs the check always (even when the regular
     expression for the architecture does not match).
+
   - `relocate_paths`: a list of toplevel paths scanned recursively to perform
     relocation of executables and dynamic libraries **on macOS only**. If not
     specified, defaults to `bin`, `lib` and `lib64`.

docs/docs/troubleshooting.md

@@ -76,8 +76,9 @@ will tell you something like:
     We will build packages in the following order: defaults-release AliEn-CAs GMP UUID gSOAP ApMon-CPP GEANT4 boost MPFR MonALISA-gSOAP-client cgal XRootD fastjet xalienfs AliEn-Runtime ROOT vgm GEANT3 GEANT4_VMC AliRoot
 
 If you have a system package which you think should be used but it's not, you
-can run `aliDoctor <package-name>` to try to understand why that was the case
-(or you can [open a bug report](https://github.com/alisw/alidist/issues) with its output and we will look at it).
+can run `aliBuild doctor <package-name>` to try to understand why that was the
+case (or you can [open a bug report](https://github.com/alisw/alidist/issues)
+with its output and we will look at it).
 
 ### What is PIP ? How do I install it?
 
@@ -155,7 +156,7 @@ it means that aliBuild does not consider you system tool good enough to
 be compatible with the one provided by the recipe. You can verify what
 happens during the system tool detection by running:
 
-    aliDoctor <package name>
+    aliBuild doctor <package name>
 
 
 ### AliBuild fails with `cannot open file "AvailabilityMacros.h`
@@ -236,7 +237,7 @@ building unless one of the system dependencies is absolutely required
 tool, where simply installing them might be a better option. For this
 reason we suggest that users run:
 
-    aliDoctor AliPhysics
+    aliBuild doctor AliPhysics
 
 in the same path where their `alidist` folder is, before actually
 starting to build, so that they can get an overview of what will be

docs/docs/user.md

@@ -11,7 +11,9 @@ For a quick start introduction, please look [here](quick.md).
 aliBuild build [-h] [--defaults DEFAULT]
                [-a ARCH] [--force-unknown-architecture]
                [-z [DEVELPREFIX]] [-e ENVIRONMENT] [-j JOBS] [-u]
-               [--no-local PKGLIST] [--disable PACKAGE]
+               [--no-local PKGLIST] [--force-tracked] [--disable PACKAGE]
+               [--force-rebuild PACKAGE] [--annotate PACKAGE=COMMENT]
+               [--only-deps] [--plugin PLUGIN]
                [--always-prefer-system | --no-system]
                [--docker] [--docker-image IMAGE] [--docker-extra-args ARGLIST] [-v VOLUMES]
                [--no-remote-store] [--remote-store STORE] [--write-store STORE] [--insecure] 
@@ -39,7 +41,18 @@ aliBuild build [-h] [--defaults DEFAULT]
   given.
 - `--no-local PKGLIST`: Do not pick up the following packages from a local
   checkout. `PKGLIST` is a comma-separated list.
+- `--force-tracked`: Do not pick up any packages from a local checkout.
 - `--disable PACKAGE`: Do not build `PACKAGE` and all its (unique) dependencies.
+- `--force-rebuild PACKAGE`: Always rebuild the specified packages from scratch,
+  even if they were built before. Has the same effect as adding
+  `force_rebuild: true` to the recipe. May be specified multiple times or
+  separate multiple arguments with commas.
+- `--annotate PACKAGE=COMMENT`: Store `COMMENT` in the build metadata for
+  `PACKAGE`. The comment will only be stored if the package is compiled or
+  downloaded during this run. May be specified multiple times.
+- `--only-deps`: Only build dependencies, not the main package. Useful for
+  populating a build cache.
+- `--plugin PLUGIN`: Plugin to use for the build. Default is `legacy`.
 - `--always-prefer-system`: Always use system packages when compatible.
 - `--no-system`: Never use system packages, even if compatible.
 
@@ -102,8 +115,8 @@ provides tarballs for the most common supported architectures.
 
 ## Using precompiled packages
 
-By running aliBuild with no special option on CentOS/Alma 7, 8 or 9, or on
-Ubuntu 20.04, 22.04 or 24.04, it will automatically try to
+By running aliBuild with no special option on CentOS/Alma 7, 8 or 9 (x86-64 or ARM),
+or on Ubuntu 20.04, 22.04 or 24.04 (x86-64), it will automatically try to
 use as many precompiled packages as possible by downloading them from a default
 central server. By using precompiled packages you lose the ability to pick some
 of them from your system. If you do not want to use precompiled packages and you
@@ -199,16 +212,30 @@ case the incremental recipe will always be executed.
 
 While alibuild does its best to find out which OS / distribution you are
 using, sometimes it might fail to do so, for example in the case you
-start using a new *buntu flavour or a bleeding edge version of Centos.
-In order to force the the correct architecture for the build you can use
+start using a new *buntu flavour or a bleeding edge version of a distribution.
+In order to force the correct architecture for the build you can use
 the `--architecture` (`-a`) flag with one of the supported options:
 
-- `slc5_x86-64`: Scientific Linux 5 and compatibles, on Intel / AMD x86-64.
-- `slc6_x86-64`: Scientific Linux 6 and compatibles, on Intel / AMD x86-64.
-- `slc7_x86-64`: CERN Centos 7 and compatibles, on Intel / AMD x86-64.
-- `ubuntu1404_x86-64`: Ubuntu 1404 and compatibles, on Intel / AMD x86-64.
-- `osx_x86-64`: OSX, on Intel / AMD x86-64.
-- `slc7_ppc64`: RHEL7 on POWER8 (LE only for now).
+On Linux, x86-64:
+- `slc6_x86-64`: RHEL6 / SLC6 compatible
+- `slc7_x86-64`: RHEL7 / CC7 compatible
+- `slc8_x86-64`: RHEL8 / CC8 compatible
+- `slc9_x86-64`: RHEL9 / ALMA9 compatible
+- `ubuntu2004_x86-64`: Ubuntu 20.04 compatible
+- `ubuntu2204_x86-64`: Ubuntu 22.04 compatible
+- `ubuntu2404_x86-64`: Ubuntu 24.04 compatible
+- `fedora33_x86-64`: Fedora 33 compatible
+- `fedora34_x86-64`: Fedora 34 compatible
+
+On Linux, ARM:
+- `slc9_aarch64`: RHEL9 / ALMA9 compatible
+
+On Linux, POWER8 / PPC64 (little endian):
+- `slc7_ppc64`: RHEL7 / CC7 compatible
+
+On Mac:
+- `osx_x86-64`: Intel
+- `osx_arm64`: Apple Silicon
 
 ### Running in Docker
 
@@ -234,27 +261,33 @@ option using the same syntax used by Docker.
 
 ## Defaults
 
-By default `aliBuild` is tuned to build the production version of ALICE
-Offline software, as deployed on the Grid, so some of the choices in
-terms of version of the packages and compilation flags are tweaked for
-that. For example, ROOT5 is used because that's what is what has been
-validated for datataking and the choice will not change until the end of
-RUN2 of LHC. In order to change that and use, for example, a more recent
-version of ROOT you can use the `--default root6` option which will
-enable ROOT6 based builds. For a more complete description of how defaults
-works please look at [the reference manual](reference.md#defaults).
+By default, `aliBuild` uses the `o2` defaults (`--defaults o2`), which are
+optimized for building the ALICE O2 software stack. The defaults system
+allows you to specify different sets of build configurations, compiler
+flags, and package versions through the `--defaults` option.
+
+Different defaults can be used to:
+- Use different package versions (e.g., different ROOT versions)
+- Apply specific compiler flags (e.g., debug builds, optimization levels)
+- Enable or disable certain features or packages
+
+To use a different set of defaults, use the `--defaults <name>` option,
+which will load settings from `CONFIGDIR/defaults-<name>.sh`. For example,
+`--defaults o2-epn` would use the `defaults-o2-epn.sh` file.
+
+For a more complete description of how the defaults system works and how to
+create custom defaults, please look at [the reference manual](reference.md#defaults).
 
 ## Disabling packages
 
 You can optionally disable certain packages by specifying them as a comma
 separated list with the `--disable` option.
 
-Moreover, starting from aliBuild 1.4.0, it will also be
-possible to disable packages by adding them to the `disable`
-keyword of your defaults file (see previous paragraph). See the
+It's also possible to disable packages by adding them to the `disable` keyword
+of your defaults file (see previous paragraph). See the
 [defaults-o2.sh](https://github.com/alisw/alidist/blob/master/defaults-o2.sh)
-file for an example of how to disable `AliEn-Runtime` and `AliRoot`
-when passing `--defaults o2`.
+file for an example of how to disable `mesos` and `MySQL` when
+passing `--defaults o2`.
 
 ## Controlling which system packages are picked up
 
@@ -294,15 +327,12 @@ installation area.
 
 ## Upgrading aliBuild
 
-aliBuild is installed via `pip`. In order to upgrade it on most laptops (in
-particular Macs) do:
+aliBuild can be installed either via `pip`, or by your OS package manager (more info [here](https://alice-doc.github.io/alice-analysis-tutorial/building/custom.html). 
 
-    pip install --upgrade alibuild
+The way to upgrade it depends on your installation method. If you installed it
+via `pip`, you can upgrade it by running:
 
-or in case you need to be root (_e.g._ on Ubuntu and most Linux distributions
-for convenience):
-
-    sudo pip install --upgrade alibuild
+    pip install --upgrade alibuild
 
 In general updating aliBuild is safe and it should never trigger a rebuild or
 break compilation of older versions of alidist (i.e. we do try to guarantee
@@ -315,10 +345,8 @@ when running the command.
 You can also upgrade / install a specific version of alibuild by specifying it on the 
 command line. E.g.:
 
-    pip install alibuild=1.5.5.rc1
+    pip install alibuild=1.17.23
     
-this is in particular required when you want to try out release candidates (rc) builds which
-are masked out by default.
 
 ## Rebuilding packages from branches instead of tags
 
@@ -339,11 +367,11 @@ server-side pull request checks).
 
 ## Generating a dependency graph
 
-It is possible to generating a PDF with a dependency graph using the `aliDeps`
+It is possible to generating a PDF with a dependency graph using the `aliBuild deps`
 tool. Assuming you run it from a directory containing `alidist`, and you have
 Graphviz installed on your system, you can simply run:
 
-    aliDeps O2 --outgraph graph.pdf
+    aliBuild deps O2 --outgraph graph.pdf
 
 The example above generates a dependency graph for the package `O2`, and saving
 the results to a PDF file named `graph.pdf`. This is what the graph looks like:
@@ -357,13 +385,25 @@ others (this can indicate an error in the recipes).
 Connections are color-coded as well: blue connections indicate a runtime
 dependency whereas a grey connection indicate a build dependency.
 
-By default, `aliDeps` runs the usual system checks to exclude packages that can
+By default, `aliBuild deps` runs the usual system checks to exclude packages that can
 be taken from the system. If you want to display the full list of dependencies,
 you may want to use:
 
-    aliDeps O2 --no-system --outgraph graph.pdf
+    aliBuild deps O2 --no-system --outgraph graph.pdf
+
+Additional useful options for `aliBuild deps` include:
+
+- `--neat`: Produce a graph with transitive reduction, removing edges that are
+  implied by other paths in the graph. This can make complex dependency graphs
+  easier to read.
+- `--outdot FILE`: Keep the intermediate Graphviz dot file in `FILE`. Useful if
+  you want to manually modify the graph or generate output in different formats.
+
+For example, to generate a simplified graph and keep the dot file:
+
+    aliBuild deps O2 --neat --outdot graph.dot --outgraph graph.pdf
 
-Please run `aliDeps --help` for further information.
+Please run `aliBuild deps --help` for further information.
 
 ## Using the packages you have built
 

docs/README.md

@@ -1 +0,0 @@
-Read the documentation here: <http://alisw.github.io/alibuild/>