Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add more depth to Flake input #2812

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

toastal
Copy link
Contributor

@toastal toastal commented Jan 30, 2025

At present, if a user copy-pastes the current documentation, a version of Nixpkgs will be added to their flake.lock lockfile. This is probably not what the user wants as Nixpkgs, the tarball, is quite large & the user likely expects the StevenBlack Flake to be used as a module to just be using the Nixpkgs of the system.

This change should also help new Nix users know how to pin a Nix version if there ever comes a time where the Nix API changes—even if lib tries to be stable & backwards-compatible.

Additionally, provide a comment about where & what the input can be—such as a mirror or a local fork for development.


Also has been open @ https://gitlab.com/StevenBlack/hosts/-/merge_requests/1

@toastal toastal force-pushed the nix-docs-flake-follows-input branch from 69f08a7 to f889a12 Compare February 1, 2025 12:11
@StevenBlack
Copy link
Owner

StevenBlack commented Feb 1, 2025

Thank you for this @toastal.

This repository has 31 different variants, so we have 31 separate readme.md files, and they are all auto-generated from a template.

Changes to readme.md should be made in readme_template.md.

At present, if a user copy-pastes the current documentation, a version
of Nixpkgs will be added to their ``flake.lock`` lockfile. This is
probably not what the user wants as Nixpkgs, the tarball, is quite large
& the user likely expects the StevenBlack Flake to be used as a module
to just be using the Nixpkgs of the system.

This change should also help new Nix users know how to pin a Nix version
if there ever comes a time where the Nix :ac:`API` changes—even if ``lib``
tries to be stable & backwards-compatible.

Additionally, provide a comment about where & what the input can be—such
as a mirror or a local fork for development.

Format: text/x-rst
@toastal toastal force-pushed the nix-docs-flake-follows-input branch from f889a12 to 72a93d1 Compare February 1, 2025 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants