| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The nixpkgs manual contains references to both sri hash and explicit
sha256 attributes. This is at best confusing to new users. Since the
final destination is exclusive use of sri hashes, see nixos/rfcs#131,
might as well push new users in that direction gently.
Notable exceptions to sri hash support are builtins.fetchTarball,
cataclysm-dda, coq, dockerTools.pullimage, elixir.override, and
fetchCrate. None, other than builtins.fetchTarball, are fundamentally
incompatible, but all currently accept explicit sha256 attributes as
input. Because adding backwards compatibility is out of scope for this
change, they have been left intact, but migration to sri format has been
made for any using old hash formats.
All hashes have been manually tested to be accurate, and updates were
only made for missing upstream artefacts or bugs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The `sparseCheckout` argument allows the user to specify directories or
patterns of files, which Git uses to filter files it should check-out.
Git expects a multi-line string on stdin ("newline-delimited list", see
`git-sparse-checkout(1)`), but within nixpkgs it is more consistent to
use a list of strings instead. The list elements are joined to a
multi-line string only before passing it to the builder script.
A deprecation warning is emitted if a (multi-line) string is passed to
`sparseCheckout`, but for the time being it is still accepted.
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |
|
| |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |
|
| |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |
|
| |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |
|
| |
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |
|
| |
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
… and link from the coding-conventions chapter to it.
Closes #48569.
|
| |\
| |
| | |
doc/builders: fix typos
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
| |
doc/builders/fetchers.chapter.md: fetcheres -> fetchers
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We are still using Pandoc’s Markdown parser, which differs from CommonMark spec slightly.
Notably:
- Line breaks in lists behave differently.
- Admonitions do not support the simpler syntax https://github.com/jgm/commonmark-hs/issues/75
- The auto_identifiers uses a different algorithm – I made the previous ones explicit.
- Languages (classes) of code blocks cannot contain whitespace so we have to use “pycon” alias instead of Python “console” as GitHub’s linguist
While at it, I also fixed the following issues:
- ShellSesssion was used
- Removed some pointless docbook tags.
|
| | |
|
| |\
| |
| | |
Add fetcher: fetchFromSourcehut
|
| | | |
|
| |/ |
|
| |
|