znippy-plugin-rust-toolchain 0.1.0

Airgapped Rust-toolchain bundle metadata plugin for znippy (native builtin — no WASM)
Documentation
  • Coverage
  • 94.74%
    18 out of 19 items documented0 out of 7 items with examples
  • Size
  • Source code size: 54.21 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 834.97 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 1m Average build duration of successful builds.
  • all releases: 1m 32s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Repository
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • Ignalina

znippy handler for airgapped Rust-developer bundles — the rust-dev-rhel8-<ver>.znippy payload (a standalone rustup-dist toolchain + a cargo vendor crate set + a .cargo/config + pinned integrity manifest) that lets a disconnected RHEL 8 box cargo build/cargo run offline.

It teaches znippy's Arrow-IPC index what each entry of a sealed rust-dev bundle is, so the archive is self-describing and DuckDB/Polars-queryable (SELECT logical_path FROM bundle WHERE member_kind = 'vendor-crate'). It adds only metadata columns — the format, the pack/move/unfold mechanics and the sealing stay owned by znippy + Skidbladnir.

Native builtin: registered in znippy-cli/src/handlers.rs::builtin_handlers, discovered via [ArchiveTypePlugin::meta]. NOT a WASM plugin. Sibling of znippy-plugin-skidbladnir (type_id 40) — a fresh type_id (41) so a znippy meta query over a toolchain bundle is unambiguous (design decision §6.2).

Laws it honours: P-1 one archive = one ecosystem (--format rust-toolchain); P-2 writes only the columns it declared; P-4 never panics — a member it cannot parse still writes with its path-derived member_kind, only the optional toolchain_version/host_triple degrade to null.