eggup-eggpack 0.1.2

Optional Eggpack ReleaseManifest adapter for Eggup deployment inputs (no release policy, authenticity, or destination selection)
Documentation
1
2
3
4
5
6
7
8
9
10
11
# eggup-eggpack

Optional adapter from Eggpack ReleaseManifest v1 to caller-owned Eggup acquisition and deployment inputs.

Direct and bundle layouts can be projected, bound to exact caller URLs, and materialized as an `ArtifactSet` after exact-size checks. Archive layouts flow through the qualified extraction handoff: `validate_acquired_archive` proves archive path/size/digest continuity, `archive_format_for_name` maps the caller-selected artifact name to a supported format (fail-closed), `archive_plan_for` builds the `eggup_archive::ArchivePlan` with exact member size/digest facts, `core_plan_for_archive` builds the core `InstallPlan` while advisory paths are valid, and `bind_archive_members` transfers open member objects into `BoundSources` for `InstallPlan::prepare_with_bound_sources`. The helpers perform no extraction, commit, or cleanup themselves; I/O orchestration and deferred `DeferredCleanup` stay caller-owned. The adapter does not choose URLs, installation roots, ownership, permissions, release policy, or authenticity. SHA-256 is integrity evidence only.

Consumers that fetch manifest bytes should call `project_json(&bytes, canonical_target)`. This applies Eggpack's published document-size bound, delegates UTF-8/schema parsing to `eggpack-manifest`, and returns sanitized adapter errors. Consumers that already hold a parsed `ReleaseManifest` may continue to call `project`.

Manifest `install` values are producer default identity only; they do not authorize replacement of a filesystem destination. `ManifestProjection::default_destinations` exposes that default map with no I/O, and `materialize_artifact_set` / `core_plan_for_archive` use it as compatibility wrappers that preserve prior behavior. Consumers with their own destination policy — for example, updating the exact running executable in place, including a renamed basename — call `materialize_artifact_set_with_destinations` or `core_plan_for_archive_with_destinations` with an exact `MemberId` -> destination map. Missing, extra, or colliding destinations fail closed; invalid destinations fail through Eggup destination validation. Member identity, exact size, SHA-256 evidence, acquired-file relationships, and permission intent are unchanged, and replacement authorization stays downstream in `eggup-core` ownership verification at commit time.

The crate is published to crates.io and depends on the published `eggpack-manifest 0.1.0` registry crate. Manifest evidence is producer-established input only: the adapter selects no release, verifies no authenticity, and authorizes no destination. SHA-256 is integrity evidence only. Lower Eggup crates remain independent of Eggpack's producer build, CI, and bootstrap crates.