aliBuild

#!/bin/bash
# SPDX-FileCopyrightText: 2015-2026 CERN
# SPDX-License-Identifier: GPL-3.0-or-later

# aliBuild — backward-compatible wrapper around bits.
#
# Reproduces the original aliBuild behaviour and module-listing output
# (e.g. "VO_ALICE@zstd::1.5.7-local1") WITHOUT needing or creating a bits.rc.
# It exports the ALICE settings as environment variables and execs bits:
#   BITS_ORGANISATION  selects ALICE's registry/provider "home" repo
#   BITS_PKG_PREFIX    the display prefix shown by `bits q`
#   BITS_BRANDING      cosmetic program name
# Plain `bits` (no organisation, no prefix) prints native "<pkg>/<version>".
export BITS_ORGANISATION="${BITS_ORGANISATION:-ALICE}"
export BITS_PKG_PREFIX="${BITS_PKG_PREFIX:-VO_ALICE}"
export BITS_BRANDING="${BITS_BRANDING:-aliBuild}"
# Legacy aliBuild emulation. BITS_BRANDING=aliBuild selects the legacy path:
#  - recipes come from a local alidist checkout (`aliBuild init`), NOT the
#    bits-providers bootstrap (that "provider path" is the default for native
#    `bits`). bits.bits_providers therefore defaults to empty under aliBuild;
#    set BITS_PROVIDERS=... explicitly to opt back in.
#  - the legacy build-time init.sh is kept (BITS_LEGACY_INITDOTSH=1): its hashes
#    are byte-identical to the pre-modules default, so bits and aliBuild can still
#    share tarballs. Override with BITS_LEGACY_INITDOTSH=0 / --initdotsh-from-modules.
export BITS_LEGACY_INITDOTSH="${BITS_LEGACY_INITDOTSH:-1}"
# Config-dir default: aliBuild keeps the legacy `alidist` convention (recipes in
# a local alidist checkout), whereas plain `bits` defaults to the current
# directory (you are normally inside a recipe repo). BITS_REPO_DIR seeds the
# --config-dir default in args.py; an explicit --config-dir still overrides it.
export BITS_REPO_DIR="${BITS_REPO_DIR:-alidist}"
exec "$(dirname "$0")/bits" "$@"