-
Notifications
You must be signed in to change notification settings - Fork 0
Migrate nixpkgs flake url to tarball #81
Copy link
Copy link
Open
Labels
compat: backwardsRepresents a backwards compatible change. Existing functionality is wholly unaffected by changes.Represents a backwards compatible change. Existing functionality is wholly unaffected by changes.priority: lowNon-essential issues that are neither affecting functionality nor usability.Non-essential issues that are neither affecting functionality nor usability.type: feature/additionMarks the request/implementation of a feature addition. Accompany with relevant labels.Marks the request/implementation of a feature addition. Accompany with relevant labels.
Description
Activity
Metadata
Metadata
Assignees
Labels
compat: backwardsRepresents a backwards compatible change. Existing functionality is wholly unaffected by changes.Represents a backwards compatible change. Existing functionality is wholly unaffected by changes.priority: lowNon-essential issues that are neither affecting functionality nor usability.Non-essential issues that are neither affecting functionality nor usability.type: feature/additionMarks the request/implementation of a feature addition. Accompany with relevant labels.Marks the request/implementation of a feature addition. Accompany with relevant labels.
Basically, we want to change from this:
to this:
Why? Less reliance on GitHub, which has been showing more and more signs of being unreliable with all of the recent news of GitHub going down arbitrarily. There's another benefit that the tarballs contain a cache that can be used with
command-not-found, which could makenix-indexobsolete. Minor change, might target it for this staging cycle.Minor issue pertains to our current mechanism of syncing
flake.lockrevisions across projects, which relies on using a specific commit hash, which is NOT possible if we start using tarballs. That might pose an issue (see theenvrcfile intemplates/if you want to see what I'm talking about).