Open
Conversation
This enables users who use the Nix package manager (see https://nixos.org/explore.html) to easily try out jless, and include it in a machine or user environment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm not sure if you'll want this or not (absolutely no problem if not!) but offering it in case.
The Nix package manager runs on Linux and macOS, often in addition to the system package manager. One of its features ("flakes") enables people to use packages even when not managed by the central package repo. With this addition, for example, someone can try out jless simply by running
(which if not already cached, downloads and builds the executable). More usefully, the "overlay" in
flake.nixmakes it easy to incorporate jless into a nix-managed reproducible+declarative environment (whether that's just a user environment, or an entire linux system).These two files here don't have to change with the usual release cycle (eg they pick up the name/version from
Cargo.toml). So they shouldn't be a maintenance burden, just additive.