bound 0.2.1

Binaries of bound 0.2.1 for Linux (static), macOS and Windows. Checksums in SHA256SUMS.

Fixed

• Windows: the paths bound gives programs (BOUND_ROOT, bundled PATH entries, the working directory) are spelled natively, however the caller spells the cache (BOUND_CACHE_DIR) and temporary (TMP, TEMP) directories. C:/Users/…, as Git Bash writes it, reaches programs as C:\Users\…. Drive letters, junctions and 8.3 names stay as spelled, as Windows reports a started program's own path.

Docs

• README: use the launcher of the same release. An older launcher refuses an artifact in a format it does not know, and bound build cannot tell.

The artifact format is unchanged: version 1, or version 2 for artifacts that use --cwd @bundle:DIR, --env-prepend or --env-append.

bound 0.2.0

Binaries of bound 0.2.0 for Linux (static), macOS and Windows. Checksums in SHA256SUMS.

New

• --cwd @bundle:DIR runs the program in a directory of the bundle.
• --env-prepend NAME=VALUE and --env-append NAME=VALUE put entries before or after the caller's value of a list variable such as PATH, joined with the platform's separator (:, or ; on Windows). An entry is a literal, @file:PATH or @bundle:PATH, and may not contain the separator. A bundled directory put first on PATH lets programs started by name find the bundled ones.

Format

• An artifact that uses either option is format version 2, which bound 0.2.0 or later reads (to run, inspect or verify it). Every other artifact is still written in format 1, which bound 0.1.0 reads.
• List entries count toward a new limit of 100,000 per manifest, checked before they are read.

bound 0.1.0

Binaries of bound 0.1.0 for Linux (static), macOS and Windows. Checksums in SHA256SUMS.