1 distributionPackage
A tool for packaging a set of files for distribution using a YAML manifest definition from the packageManifest project.
1.1 Main Features
Simple default operation
zip or tar-gzip package generation (or both)
Specify project path to build package from
Append manifest files to an existing tar or zip package
1.2 Installation
The simplest way to acquire distributionPackage is using pip.
pip install distributionPackage
It’s highly recommended that you install the package into a Python virtual environment.
1.3 Getting Started
Define a package manifest in a YAML file. The default name expected by distributionPackage is manifest.yml. The example below constructs a simple manifest for a hypothetical C++ project.
- include:
files: [ 'README.md', 'LICENSE', 'VERSION' ]
- global-include:
files: [ '*.h', '*.cpp' ]
- prune:
directory: 'scripts'
Assuming that you have installed distributionPackage and that the makePackage command is in your path,
makePackage
By default makePackage will acquire the manifest definitions from ./manifest.yml, output a file distribution-out.tar.gz in the current directory and assume that the current directory is the root directory of the project to be packaged (for the basis of constructing the package file names from the manifest).
Multiple manifest files may also be specified using the --manifests argument. The YAML data from the files are concatenated in the same order as the file names into a single manifest.
Using the --help option will describe the various options available.
> makePackage --help
usage: makePackage [-h] [-a] [-m [MANIFEST_PATH [MANIFEST_PATH ...]]]
[-o OUTPUT] [-p PACKAGE] [-r PROJECTROOT] [-n] [-z]
Build a distribution package from a manifest
optional arguments:
-h, --help show this help message and exit
-a, --append Append to an existing distribution package, if it
exists. Created otherwise. (default disabled)
-m [MANIFEST_PATH [MANIFEST_PATH ...]], --manifests [MANIFEST_PATH [MANIFEST_PATH ...]]
Manifest file(s) to use to build the package. (default
manifest.yml)
-o OUTPUT, --output OUTPUT
Directory to place the generated distribution files.
Created if not present. (default ./)
-p PACKAGE, --package PACKAGE
Filename stub of output package, not including suffix
or version info. (default distribution-out)
-r PROJECTROOT, --project-root PROJECTROOT
Project root to package files from. (default ./)
-n, --no-tar Disable tar, gzip output distribution. (default
enabled)
-z, --zip Enable zip output distribution. (default disabled)
1.4 DOI Archive
0.3.0 |
|
0.4.0 |
|
0.5.0 |
|
0.6.0 |
Metadata
Release files for distributionPackage 0.8.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 |
|---|---|---|---|---|
| distributionPackage-0.8.0.tar.gz | 26.8 kB | Without provenance | Details for distributionPackage-0.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| distributionPackage-0.8.0-py3-none-any.whl | Python 3 | none | any | Details for distributionPackage-0.8.0-py3-none-any.whl |
Total release size: 151.4 kB
Release files / distributionPackage-0.8.0.tar.gz
| Download URL | distributionPackage-0.8.0.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f499f5c01a397225c2282f706b40840857c6676da1460a936e0c84f4245e314e
|
|
BLAKE2b-256 checksum How to use checksums |
0f24156a8ddc3397cff0618e3427437da713973db6520d91ad58c13de271845e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.18.4
|
Release files / distributionPackage-0.8.0-py3-none-any.whl
| Download URL | distributionPackage-0.8.0-py3-none-any.whl |
|---|---|
| Size | 124.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3652fab9b10c6a02c8b1ee037a8972f76dbf936c81bcd190861de1bbe7c0b983
|
|
BLAKE2b-256 checksum How to use checksums |
5b6a48c56947f81623787c8631a5d64d8b82671e472a383a1d48ef1481445338
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.18.4
|
Security for distributionPackage 0.8.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.