Unverified Commit 15ed8f76 authored by Vladimír Čunát's avatar Vladimír Čunát Committed by GitHub
Browse files

staging-next 2025-09-21 (#444862)

parents ee5dae58 17eefed8

.git-blame-ignore-revs

+3 −0
Original line number Diff line number Diff line
@@ -264,6 +264,9 @@ a4f7e161b380b35b2f7bc432659a95fd71254ad8 
# haskellPackages.hercules-ci-agent (cabal2nix -> nixfmt-rfc-style)

9314da7ee8d2aedfb15193b8c489da51efe52bb5



# haskell-updates: nixfmt-rfc-style

9e296dcf846294e0aa94af7d3235e82eee7fe055



# nix-builder-vm: nixfmt-rfc-style

a034fb50f79816c6738fb48b48503b09ea3b0132

README.md

+1 −1
Original line number Diff line number Diff line
@@ -57,7 +57,7 @@ When successful build and test criteria are met, the Nixpkgs expressions are dis 
# Contributing



Nixpkgs is among the most active projects on GitHub.

While thousands of open issues and pull requests might seem a lot at first, it helps consider it in the context of the scope of the project.

While thousands of open issues and pull requests might seem like a lot at first, it helps to consider it in the context of the scope of the project.

Nixpkgs describes how to build tens of thousands of pieces of software and implements a Linux distribution.

The [GitHub Insights](https://github.com/NixOS/nixpkgs/pulse) page gives a sense of the project activity.

ci/eval/README.md

+1 −1
Original line number Diff line number Diff line
@@ -8,7 +8,7 @@ Furthermore it also allows local evaluation using: 
nix-build ci -A eval.baseline

```



The most important two arguments are:

The two most important arguments are:

- `--arg evalSystems`: The set of systems for which `nixpkgs` should be evaluated.

  Defaults to the four official platforms (`x86_64-linux`, `aarch64-linux`, `x86_64-darwin` and `aarch64-darwin`).

  Example: `--arg evalSystems '["x86_64-linux" "aarch64-darwin"]'`

doc/README.md

+2 −2
Original line number Diff line number Diff line
@@ -408,7 +408,7 @@ Though this is not shown in the rendered documentation on nixos.org. 


#### Footnotes



To add a foonote explanation, use the following syntax:

To add a footnote explanation, use the following syntax:



```markdown

Sometimes it's better to add context [^context] in a footnote.
@@ -443,7 +443,7 @@ This syntax is taken from [CommonMark](https://spec.commonmark.org/0.30/#link-re 
#### Typographic replacements



Typographic replacements are enabled.

Check the [list of possible replacement patterns check](https://github.com/executablebooks/markdown-it-py/blob/3613e8016ecafe21709471ee0032a90a4157c2d1/markdown_it/rules_core/replacements.py#L1-L15).

Check the [list of possible replacement patterns](https://github.com/executablebooks/markdown-it-py/blob/3613e8016ecafe21709471ee0032a90a4157c2d1/markdown_it/rules_core/replacements.py#L1-L15).



## Getting help

doc/build-helpers.md

+2 −2
Original line number Diff line number Diff line
@@ -9,7 +9,7 @@ This is not to be confused with the [`builder` argument of the Nix `derivation` 
Such a function is usually designed to abstract over a typical workflow for a given programming language or framework.

This allows declaring a build recipe by setting a limited number of options relevant to the particular use case instead of using the `derivation` function directly.



[`stdenv.mkDerivation`](#part-stdenv) is the most widely used build helper, and serves as a basis for many others.

[`stdenv.mkDerivation`](#part-stdenv) is the most widely used build helper and serves as a basis for many others.

In addition, it offers various options to customize parts of the builds.



There is no uniform interface for build helpers.