Transport original Git objects for offline source preparation #194

Open
opened 2026-10-24 13:57:53 +02:00 by erikinkinen · 1 comment
Owner

Problem and motivation

Offline source bundles retain the original source tree, generated locks and Cargo graph, but cannot yet supply a fresh Git or Cargo process with the original repository objects. Copying a Cargo cache would conceal inputs and would not establish a fresh source preparation.

Proposed behavior and scope

Add original loose or paired pack/index objects and shallow boundaries to version 4 of the existing build inventory, with an explicit object root. Export the captured object selection for every source role. Add a concrete offline provider that creates fresh controlled Git contexts, verifies their commit, tree and blob identities, and feeds a fresh Cargo operation. Preserve versions 1–3.

Authority, security and reliability

Export borrows the actual registered source owner. Offline admission holds and checks the selected object namespace; serialized records do not recreate custody or native success. Fresh Git and Cargo tools, source and output roots, work limits and deadlines are explicit. The provider has no network acquisition fallback. Preserve distinct roles, original manifests and commits, first failures, partial evidence and once-only cleanup. Hashes and Git integrity checks do not authenticate a publisher.

Acceptance criteria

  • Bind the complete captured loose/pack selection, modes, hashes, original commit/tree and shallow boundaries to each source role in the same inventory.
  • Export through actual registered source owners and protected held inputs, without repository metadata, caches or targets.
  • Admit exact offline object namespaces and immutable selections; reject missing, extra, substituted, mis-moded or unpaired objects.
  • Create fresh controlled contexts and source owners with actual Git integrity, tree and blob checks, retaining acquisition and cleanup uncertainty.
  • Add the concrete offline provider and a genuine fresh Cargo/source/lock/graph round trip that preserves original identities after the old fixture stores are unavailable.
  • Cover loose, packed and shallow inputs, distinct roles, malformed objects, cancellation and resource failures; update component and technical documentation.

Alternatives and tradeoffs

Transporting only checked-out files is useful for inspection but cannot satisfy Cargo's Git source resolution. Copying a prior cache hides its provenance. Original objects allow independent Git verification, at the cost of transporting the full captured selection, which can exceed the selected tree. Packed size does not bound decompression or build storage, so enclosing native resource limits remain necessary.

Tracking and rollout

Extends source bundles, generated locks and portable Cargo graphs. Tracked by Phase 6 completion. Guest-native tools, installation and the full EriX and external toolchain rebuilds remain separate requirements.

## Problem and motivation Offline source bundles retain the original source tree, generated locks and Cargo graph, but cannot yet supply a fresh Git or Cargo process with the original repository objects. Copying a Cargo cache would conceal inputs and would not establish a fresh source preparation. ## Proposed behavior and scope Add original loose or paired pack/index objects and shallow boundaries to version 4 of the existing build inventory, with an explicit object root. Export the captured object selection for every source role. Add a concrete offline provider that creates fresh controlled Git contexts, verifies their commit, tree and blob identities, and feeds a fresh Cargo operation. Preserve versions 1–3. ## Authority, security and reliability Export borrows the actual registered source owner. Offline admission holds and checks the selected object namespace; serialized records do not recreate custody or native success. Fresh Git and Cargo tools, source and output roots, work limits and deadlines are explicit. The provider has no network acquisition fallback. Preserve distinct roles, original manifests and commits, first failures, partial evidence and once-only cleanup. Hashes and Git integrity checks do not authenticate a publisher. ## Acceptance criteria - [ ] Bind the complete captured loose/pack selection, modes, hashes, original commit/tree and shallow boundaries to each source role in the same inventory. - [ ] Export through actual registered source owners and protected held inputs, without repository metadata, caches or targets. - [ ] Admit exact offline object namespaces and immutable selections; reject missing, extra, substituted, mis-moded or unpaired objects. - [ ] Create fresh controlled contexts and source owners with actual Git integrity, tree and blob checks, retaining acquisition and cleanup uncertainty. - [ ] Add the concrete offline provider and a genuine fresh Cargo/source/lock/graph round trip that preserves original identities after the old fixture stores are unavailable. - [ ] Cover loose, packed and shallow inputs, distinct roles, malformed objects, cancellation and resource failures; update component and technical documentation. ## Alternatives and tradeoffs Transporting only checked-out files is useful for inspection but cannot satisfy Cargo's Git source resolution. Copying a prior cache hides its provenance. Original objects allow independent Git verification, at the cost of transporting the full captured selection, which can exceed the selected tree. Packed size does not bound decompression or build storage, so enclosing native resource limits remain necessary. ## Tracking and rollout Extends [source bundles](https://git.erikinkinen.fi/erix/integration/issues/191), [generated locks](https://git.erikinkinen.fi/erix/integration/issues/192) and [portable Cargo graphs](https://git.erikinkinen.fi/erix/integration/issues/193). Tracked by [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Guest-native tools, installation and the full EriX and external toolchain rebuilds remain separate requirements.
Author
Owner

Signed local commits now add version-four bundles with original Git objects and shallow boundaries. The offline provider prepares fresh contexts, source trees and Cargo results from held inputs, with no network fallback. Guest tool installation and both required builds inside EriX remain open.

Signed local commits now add version-four bundles with original Git objects and shallow boundaries. The offline provider prepares fresh contexts, source trees and Cargo results from held inputs, with no network fallback. Guest tool installation and both required builds inside EriX remain open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:22 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#194
No description provided.