Files
MX_Pmodule/ccp4/README.md
T
duan_jandClaude Fable 5 273569c87e Add ccp4 module: vendor tarball, non-interactive BINARY.setup
Pre-agrees the CCP4 licence via .agree2ccp4v6 so BINARY.setup never
prompts. Download via urls: with unpacker: none (untar once into PREFIX,
BINARY.setup patches paths at final location). Build tmp and download
cache go to /das/work/p21/p21515/.cache/Pmodules through
~/.Pmodules/Pmodules.yaml (see README) since /var/tmp and the home quota
are too small for the ~5 GB tarball.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-18 19:44:06 +02:00

54 lines
1.8 KiB
Markdown

# ccp4
CCP4 suite (binary distribution, bundled with SHELX and ARP/wARP) for
macromolecular crystallography. https://www.ccp4.ac.uk/
- Vendor tarball install: default `prep` downloads the ~5 GB tarball
(cached in `$PMODULES_DISTFILESDIR`), `install` untars it into `$PREFIX`
and runs `BINARY.setup`.
- Non-interactive: the CCP4 licence is pre-agreed via `.agree2ccp4v6`
before `BINARY.setup` runs, so the build never prompts.
- No `shasums:`: the download link is session-gated (`sid=` expires), so
the checksum cannot be pinned ahead of the first fetch. After the first
successful build, `sha256sum` the cached tarball and add it if wanted.
- Module version is the series (`9.0`); minor updates (9.0.xxx) come via
the CCP4 update manager inside the installation.
## Build on Ra
One-time per user: put the Pmodules build tmp and download cache on
/das instead of /var/tmp and $HOME (the tarball alone would blow the
home quota):
```bash
mkdir -p /das/work/p21/p21515/.cache/Pmodules/distfiles ~/.Pmodules
cat > ~/.Pmodules/Pmodules.yaml <<'EOF'
tmp_dir: /das/work/p21/p21515/.cache/Pmodules
download_dir: /das/work/p21/p21515/.cache/Pmodules/distfiles
EOF
```
Then:
```bash
module use unstable && module load modbuild/2.1.2
cd ccp4
modbuild build --check-mode 9.0 # yamllint the config first
modbuild build 9.0
```
If the download fails (expired sid), fetch a fresh link from
https://www.ccp4.ac.uk/download/ and update `files/config.yaml`, or drop a
hand-downloaded tarball into the distfiles dir under the `name:` given in
`files/config.yaml`.
## Verify
```bash
module use MX unstable && module load ccp4/9.0
which refmac5 ccp4i2
echo $CCP4 # should point into /opt/psi/MX/ccp4/9.0/ccp4
```
Bundled SHELX and ARP/wARP still need their own academic registrations.