feat(package): torb vendor #320
Loading…
Reference in a new issue
No description provided.
Delete branch "loop/24-torb-vendor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #24
torb vendor [--offline] [--project <dir>]copies every registry package the lock pins intovendor/<owner>/<name>/after checking each tree hash (from the cache or fetched), before a file is written.project.trbgets onesource ... path:line per copy, the lock is rewritten, and a second run changes nothing and says so. A dependency that left the graph leavesvendor/andproject.trb.--offlinenames the first package missing from the cache; no lock and path-only projects get their own messages.torb publishrefuses a project that depends on a vendored copy.compiler/src/package/vendor.trb,runVendorincli/packages.trb,withSource/withoutSourceinmanifest-edit.trbwith unit tests.tools/vendor.sh(wired intotools/gates.sh): e2e against afile:registry fixture; the vendored project builds with an empty cache and no network, the same run fails beforevendor.docs/tooling/torb-vendor.md, index andthe-torb-command.md, RELEASE.md 7.5 "As built", skills regenerated by hand (CI will show any drift).Not run locally (no bootstrap): CI is the verification.
c3854b4f7edfd01e318etorb vendor#24Reviewed at
dfd01e3. CI is green on this head (gates includes the newtools/vendor.sh; pdisc green).withSource/withoutSource; e2etools/vendor.shwired into gates (offline build with empty cache, wrong archive refused before any write, cache vs fetched copy identical, idempotent second run, stale removal).--offline, no-lock and path-only cases handled.docs/tooling/). Thepublishrefusal for vendored copies is a small, directly related guard.vendor/and thesourcelines are touched.docs/tooling/torb-vendor.md, index, command page, RELEASE.md 7.5 and the skills updated.Non-blocking: none.
torb vendor#24