| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
conventions (#297654)
* doc: improve fetchers overview, deduplicate readme content
* Improve caveat explanation and some fetchurl content
* move out consumer docs on source fetching
* move note on mirror URLs to the relevant section
this may be better suited for the `fetchurl` reference, but it's probably better to
just render that information into the manual. for now, because
- contributor documentation encourages mirrors
- we can expect contributors to dig into the source
- linking source files is trivial in in-code documentation
we leave it there.
* move instructions for updating hashes to the manual
* Add more clarity on text, reorganise source hash methods
---------
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
Co-authored-by: Dominic Mills-Howell <dominic.millz27@gmail.com>
Co-authored-by: lolbinarycat <dogedoge61+github@gmail.com>
|
|
This allows for correct highlighting and maybe future automatic
formatting. The AST was verified to work with nixfmt only.
|
|
This should help us with highlighting and future formatting.
|
|
|
|
Upstream has been archived. The current package is not installable by
default, since it depends on nix 2.15 which is marked as insecure.
|
|
I don't believe there is supposed to be two urls in the fetchers example
|
|
Signed-off-by: benaryorg <binary@benary.org>
|
|
pkgs/README.md: clarify guidelines for `meta.mainProgram`
|
|
|
|
|
|
|
|
GitHub supported special markdown syntax for emphasising blocks for some
time. This was however a beta feature, and still is, so it's subject to
changes.
Recently such a change happened: The syntax is different now.
See https://github.com/orgs/community/discussions/16925 for more
information
|
|
doc: commit header convention for documentation changes
|
|
|
|
CONTRIBUTING: Add hotlinks to package and module reviewing guides, minor touchups
|
|
references
|
|
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
|
|
|
|
|
|
|
|
[RFC 140] Simple package paths, part 1b: Enabling the directory structure
|
|
|
|
|
|
|
|
Nixpkgs is not your personal depot. Add a light decision-making
framework to help decide what fits in the project or not.
Co-authored-by: Anderson Torres <torres.anderson.85@protonmail.com>
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
Co-authored-by: Ryan Lahfa <masterancpp@gmail.com>
|
|
Also mainly covered in the section below
|
|
|
|
Moving and collecting bits into the appropriate places, also writing
some new sentences
|
|
|
|
No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.
Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.
|
|
No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.
Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.
|
|
No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.
Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.
|
|
Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.
|
|
No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.
Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.
|
|
No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.
|
|
|
