bits
Bits is a tool to build, install and package large software stacks. It originates from the aliBuild tool, originally developed to simplify building and installing ALICE / ALFA software and attempts to make it more general and usable for other communities that share similar problems and have overlapping dependencies. It is under active development and subject to rapid changes and should NOT be used in production environment where stability and backward compatibility is important.
Instant gratification with:
$ git clone git@github.com:bitsorg/bits.git; cd bits; export PATH=$PWD:$PATH; cd .. $ git clone git@github.com:bitsorg/alice.bits.git $ cd alice.bits $ git clone git@github.com:bitsorg/common.bits.git;
Review and customise bits.rc file (in particular, sw_dir location where all output will be stored):
$ cat bits.rc [bits] organisation=ALICE [ALICE] pkg_prefix=VO_ALICE sw_dir=../sw repo_dir=. search_path=common
Then:
$ bits build ROOT $ bits enter ROOT/latest $ root -b
Full documentation at:
Pre-requisites
If you are using bits 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 .
Contributing
If you want to contribute to bits, 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
The test suite only runs fully on a Linux system, but there is a reduced suite for macOS, runnable with:
tox -e darwin
You can also run only the unit tests (it’s a lot faster than the full suite) with:
pytest
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
Metadata
Release files for bitsorg 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bitsorg-0.1.1.tar.gz | 485.2 kB | With provenance | Details for bitsorg-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bitsorg-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for bitsorg-0.1.1-py3-none-any.whl |
Total release size: 981.3 kB
Release files / bitsorg-0.1.1.tar.gz
| Download URL | bitsorg-0.1.1.tar.gz |
|---|---|
| Size | 485.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7a2e28da6b32df4826a03d34f30cedec928086a3217126288a4928642628e29
|
|
BLAKE2b-256 checksum How to use checksums |
59b4f53aeb2d4e17cb8ef7ed0e13767abd90981223423a3f10b5b71f8ef99145
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 20, 2025.
Transparency logRelease files / bitsorg-0.1.1-py3-none-any.whl
| Download URL | bitsorg-0.1.1-py3-none-any.whl |
|---|---|
| Size | 496.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba8d49ed992e72030501065bac8d3510616255310f9399e23dd1e71c8172ff39
|
|
BLAKE2b-256 checksum How to use checksums |
8e7cf31faee39ae445175ce25c5d9438915d03be7a2b995eb2165f0921d89629
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 20, 2025.
Transparency logSecurity for bitsorg 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bitsorg-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 20, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.