Introduce documentation about nixpkgs and flakes at RV#14
Open
juliankuners wants to merge 1 commit into
Open
Conversation
17 tasks
Contributor
Author
|
This PR is kept as draft, in case more documentation is added. This will likely be merged once |
This was referenced May 26, 2025
automergerpr-permission-manager Bot
pushed a commit
to runtimeverification/k
that referenced
this pull request
Jun 6, 2025
…y update workflow (#4824) This pull request adapts the nix flake inputs structure regarding `nixpkgs` and `rv-nix-tools`. In particular, `nixpkgs` is now specified for inputs and transitive inputs by following an explicitly specified revision of `rv-nix-tools`. More thorough reasoning for this change is outlined in documentation added by this PR runtimeverification/rv-nix-tools#14. This change is done to make `nixpkgs` properly updatable by CI. In addition, this pull requests adapts the `update-deps.yml` workflow to also update `rv-nix-tools` that is used to implicitly specify the revision of `nixpkgs`. --------- Co-authored-by: Freeman <105403280+F-WRunTime@users.noreply.github.com>
automergerpr-permission-manager Bot
pushed a commit
to runtimeverification/haskell-backend
that referenced
this pull request
Jun 6, 2025
…for `rv-nix-tools` (#4109) This pull request adapts the nix flake inputs structure regarding `nixpkgs` and `rv-nix-tools`. In particular, `nixpkgs` is now specified for inputs and transitive inputs by following an explicitly specified revision of `rv-nix-tools`. More thorough reasoning for this change is outlined in documentation added by this PR runtimeverification/rv-nix-tools#14. This change is done to make `nixpkgs` properly updatable by CI. In addition, this pull requests adapts the `update-deps.yml` workflow to also update `rv-nix-tools` that is used to implicitly specify the revision of `nixpkgs`. --- ###### Review checklist The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed. - [x] **Summary.** Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history. - [ ] **Documentation.** Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing. - [ ] **Tests.** Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests. - [ ] **Clean up.** The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes! --------- Co-authored-by: Jost Berthold <jost.berthold@gmail.com>
automergerpr-permission-manager Bot
pushed a commit
to runtimeverification/llvm-backend
that referenced
this pull request
Jun 19, 2025
…y update workflow (#1207) This pull request adapts the nix flake inputs structure regarding `nixpkgs` and `rv-nix-tools`. In particular, `nixpkgs` is now specified for inputs and transitive inputs by following an explicitly specified revision of `rv-nix-tools`. More thorough reasoning for this change is outlined in documentation added by this PR runtimeverification/rv-nix-tools#14. This change is done to make `nixpkgs` properly updatable by CI. In addition, this pull requests adapts the `update-deps.yml` workflow to also update `rv-nix-tools` that is used to implicitly specify the revision of `nixpkgs`.
juliankuners
marked this pull request as ready for review
July 16, 2026 11:16
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.
This pull request introduces documentation that covers nix flakes, the
followsattribute of nix flake inputs, different usage patterns offollows, and howrv-nix-toolscan be used to specifynixpkgsin flakes.In addition, the documentation covers how breaking update pull requests of
nixpkgscan be properly resolved. While breaking update pull requests are very unlikely for small incremental updates ofnixpkgs, the upcoming migration from anixpkgsrevision that is over one year old to a recent revision ofnixpkgsis more likely to break nix flakes at runtime verification.