-
Notifications
You must be signed in to change notification settings - Fork 2
FAQ
The older installation script relied on precompiled libraries and tools being available for downloading to the target operating system, including ROOT. Since those precompiled packages are not maintained anymore, this build procedure is done by the script, which adds a considerable amount of extra time to its execution time.
We only support the versions you can see under Releases
. If you need any other version of any package or Python, please consider creating a custom installation package or contact [email protected]
. For DQM maintainers, see here.
No, if you already built ROOT, and you're reinstalling DQMGUI in the same directory, you will not have to build ROOT again, and the installation script will skip this step automatically (by checking the existence of the thisroot.sh
file in the location $INSTALLATION_DIR/root
, by default: /data/srv/root/bin/thisroot.sh
).
A ROOT rebuild is required for the following cases:
- You're deploying DQMGUI with a different Python version than the one used to build ROOT the first time.
- You're deploying a new version of ROOT.
Two cases:
-
You want to create a new release, which you cannot find under Releases. This means that you want to change a version of the packages downloaded, e.g. DQMGUI, or DMWM's deployment.
-
You want to update an existing release (less common, probably for debugging reasons): The release you are looking for exists, but some of the packages downloaded in this release have been updated, using the same tag/reference/branch name. For example, if you want to include a development branch of DQMGUI (e.g.
dev
), the DQMGUIdev
branch may be updated, but the installation package that has been created cloned an older version of thedev
branch.
This package is built for python3.6, making it incompatible with python3.8. Hence, we need to build it from source with python3.8.