Skip to content

Offline commands: --offline, fetch, vendor, bundle #145

Open

Description

@Kinflou

Part of ComlineProject/core#227. Proposal: ComlineProject/docs#163, proposals/offline/index.md.

  • --offline on every command (plus an environment variable and machine config): no network, with one error listing everything missing.
  • comline fetch: fetch exactly what a build would.
  • comline vendor: write every dependency into the project.
  • comline bundle export and comline bundle import.

Builds on the core issues linked from ComlineProject/core#227.

Activity

  1. Kinflou commented on Nov 9, 2026

    @Kinflou
    MemberAuthor

    Decided (docs#163). Also in scope here:

    • reading the [fetch] policy from comline.toml;
    • the layered machine and organisation config (COMLINE_CONFIG);
    • COMLINE_OFFLINE=1;
    • comline cache list and comline cache prune;
    • comline bundle import --allow-unsigned.
  2. Kinflou commented on Nov 9, 2026

    @Kinflou
    MemberAuthor

    Deferred, as agreed: whether comline fetch takes --for <target> (fetching only what one target's generation needs) is decided while implementing this, not before.

  3. Kinflou commented on Nov 12, 2026

    @Kinflou
    MemberAuthor

    The CLI now groups dependency commands under comline deps (#153: deps add, deps accept; deps remove, deps pin and deps list next). So fetch and vendor land as comline deps fetch and comline deps vendor. --offline stays global, and bundle export|import stays top-level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Soon

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions