Skip to content

Migration strategy for changing github: inputs to git:-backed implementation #13151

Open
@roberth

Description

@roberth

Is your feature request related to a problem?

Shallow git-based fetching appears to have better performance than tarball-based fetching.

They're not exactly the same, so we'll have to manage this carefully.

Proposed solution

Make use of original vs locked fields in the lock file.

Add a flag to control what's generated during locking.

New setting
Default: current behavior
Opt in: generate git-based lock node

This should be a setting, because then we can test it before we start switching the ecosystem in a future release.

Alternative solutions

Additional context

(Nix 2.24 or 2.25 did improve tarball cache performance, but it is still outperformed by git, it seems)

Checklist


Add 👍 to issues you find important.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureFeature request or proposalfetchingNetworking with the outside (non-Nix) world, input lockingflakesidea approvedThe given proposal has been discussed and approved by the Nix team. An implementation is welcome.

    Type

    No type

    Projects

    Status

    ⚖ To discuss

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions