releng-tool
Overview
releng-tool aims to provide a way for developers to tailor the building of multiple software components to help prepare packages for desired runtime environments (e.g. cross-platform portable packages, embedded targets, etc.). When building a package, assets may be located in multiple locations and may require various methods to extract, build and more. releng-tool allows developers to define a set of packages, specifying where resources should be fetched from, how packages should be extracted and the processes for patching, configuring, building and installing each package for a target sysroot.
The structure of a package depends on the specific project. The simplest type is a script-based package, where users can define custom scripts for various stages. A package does not need to handle every stage. Helper package types are available (e.g. Autotools, Cargo, CMake, Make, Meson, various Python types, SCons, Waf and Xmake) for projects using common build systems.
For detailed documentation on the releng-tool project, see releng-tool's documentation (sources).
Requirements
- Python 3.10+
Host tools such as Git, scp, etc. may be required depending on the project being processed (e.g. if a package's sources fetch from a Git source, a Git client tool is required to perform said fetch).
Installation
This tool can be installed using pip or pipx:
pipx install releng-tool
(or)
pip install -U releng-tool
(or)
python -m pip install -U releng-tool
For Arch Linux users, this package is also available on AUR:
Arch User Repository — releng-tool
https://aur.archlinux.org/packages/releng-tool/
Usage
This tool can be invoked from a command line using:
releng-tool --help
(or)
python -m releng-tool --help
Demonstration
Users can follow the tutorials found in the documentation:
releng-tool — Tutorials
https://docs.releng.io/getting-started/tutorials/
Or may inspect various test examples demonstrating various capabilities:
releng-tool — Examples Repository
https://github.com/releng-tool/releng-tool-examples
Metadata
Release files for releng-tool 4.3.0
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 |
|---|---|---|---|---|
| releng_tool-4.3.0.tar.gz | 383.5 kB | Without provenance | Details for releng_tool-4.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| releng_tool-4.3.0-py3-none-any.whl | Python 3 | none | any | Details for releng_tool-4.3.0-py3-none-any.whl |
Total release size: 668.8 kB
Release files / releng_tool-4.3.0.tar.gz
| Download URL | releng_tool-4.3.0.tar.gz |
|---|---|
| Size | 383.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d91b6043f9258ebee5ef0134cd14a581901b53e5507db0dd71749f8624dde718
|
|
BLAKE2b-256 checksum How to use checksums |
a44e194e87da4ffdae08dc417e73dc567bd20d0735e7d89ca2c242b3d0250955
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.0
|
Release files / releng_tool-4.3.0-py3-none-any.whl
| Download URL | releng_tool-4.3.0-py3-none-any.whl |
|---|---|
| Size | 285.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7eb9c7766211b6427d05a28a80ffe6a7336d4eed51b4615ec3158e35f5eddb58
|
|
BLAKE2b-256 checksum How to use checksums |
22648fa3d441a99e6114730174db32c02fb06e3cc33aeb807a24f8f4e28fd855
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.15.0
|
Security for releng-tool 4.3.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.