Packager
A command-line tool for managing Singularity images and creating executable bundles.
Installation
pip install .
Configuration
The configuration file is stored at ~/.config/packager.ini:
[packager]
singularity_path = /path/to/images
bin_path = /path/to/bin
packages_path = /path/to/packages
[images]
# This section is automatically populated by the tool
Usage
Add a set of singularity images
# From singularity_path
packager scanpackages
# From custom path
packager scanpackages --dir /qib/platforms/Informatics/transfer/outgoing/singularity/core
Add single singularity image as package
bashpackager addpackage --image /path/to/image.simg --name mypackage --version 1.0.0
Create a "HPC package" (bundle)
# Make an empty bundle
packager makebundle --name mybundle
# Make a bundle with one or more packages
packager makebundle --name denovo megahit=1.2.9 fastp=1.20.0
Add package to bundle
# By default each package is exposed as a binary called package. You can add "aliases" i.e. each binary to expose
packager addtobundle --name mybundle --package blast --version 1.0 blastn makeblastdb blastp
Metadata
Release files for nbipackager 0.0.3
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 | |
|---|---|---|---|---|
| nbipackager-0.0.3.tar.gz | 10.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nbipackager-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.4 kB
Release files / nbipackager-0.0.3.tar.gz
| Download URL | nbipackager-0.0.3.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54839ae83d2e1545bf06f71a719fc50b1299fb0569fe7462f6a9958252f49289
|
|
BLAKE2b-256 checksum How to use checksums |
36d8953a2ffcd5c10ca7b86d098f64af503b5eb441252ab95b049ffd92628f7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 7, 2025.
Transparency logRelease files / nbipackager-0.0.3-py3-none-any.whl
| Download URL | nbipackager-0.0.3-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d64f0082f244a2a7926705a73d2ac18041aa00f7138f262e361f5c82b06ee424
|
|
BLAKE2b-256 checksum How to use checksums |
3d4288370973b60245f5eea7d4ef45d537a0aafa92736f3feb7e9b1c81798919
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 7, 2025.
Transparency logSecurity for nbipackager 0.0.3
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 nbipackager-0.0.3.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 Feb 7, 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.