| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This fixes the working directory for the suggested flake, as originally
suggested by @MaxDaten in:
https://github.com/NixOS/nixpkgs/issues/229542#issuecomment-1674886874
… and then amended by @Enzime in:
https://github.com/NixOS/nixpkgs/pull/248554#issuecomment-1676825733
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Nixpkgs documentation on the linux kernel builders focused on
using and extending kernels that were already packaged, but never
mentioned that it's possible to also build a kernel almost "from
scratch".
The NixOS documentation went a bit deeper on manual linux kernel
configs, but that information wasn't particularly NixOS-specific.
This commit consolidates the information related to building the
kernel on Nixpkgs's documentation, while keeping any additional
NixOS-specific information on NixOS's documentation.
An additional README.md was created for contributor-facing
documentation.
|
| |\
| |
| | |
doc: Add lib.meta to the library functions ToC
|
| | |
| |
| |
| |
| |
| | |
This seems like a pretty easy-to-fix oversight, and it documents the
getExe function, which I never knew about until one day I saw a PR
using it. Let's include it in the manual.
|
| | |
| |
| |
| |
| | |
In x-d-p 1.17, when no configs are given, you apps will likely not
able to find a backend. Let users aware of the changes.
|
| | | |
|
| |\ \
| | |
| | | |
doc/stdenv: update manual phases execution instructions
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Update instructions for manual build phases execution via `nix-shell` to
cover all phases. There is no easy way of getting those commands, so it
makes a sense to have them all properly documented.
|
| |/ /
| |
| |
| |
| |
| | |
Previously the introductory section and the function listings were in
different places. But now nixdoc supports having them together
with https://github.com/nix-community/nixdoc/pull/70!
|
| |\ \
| | |
| | | |
buildDotnetModule small improvements
|
| | | |
| | |
| | |
| | | |
first time
|
| |\ \ \ |
|
| | | | | |
|
| |\| | | |
|
| | |\ \ \ |
|
| | | | | | |
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
was missed when qt4 was removed
|
| |\| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
- pkgs/development/libraries/gdcm/default.nix
|
| | | | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
doc: commit header convention for documentation changes
|
| | | | | | | |
|
| |\| | | | | |
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | | |
docs/javascript/introduction: fix GitHub search link
|
| | | | | | | | |
|
| |\| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | | |
Co-authored-by: Jörg Thalheim <Mic92@users.noreply.github.com>
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commits adds to the manual a tutorial showing how to
troubleshoot breakage caused by a rustc upgrade in *downstream*
packages.
|
| |\| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Using the script in maintainers/scripts/update-redirected-urls.sh
|
| |\ \ \ \ \ \ |
|
| | |\| | | | | |
|
| | | |\ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Allows splicing to work correctly
from issue 211340
>> 3: Discourage using package sets like python3.pkgs "directly"
> I think about 8 years ago I introduced this and it has been a clear mistake. Since then this pattern was copied throughout. We should indeed go to pythonPackages and also move the helpers such as buildEnv and withPackages into the package set, like haskell already had before.
- FRidh
|
| |\| | | | | | | |
|
| | |\| | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
While the word 'simply' is usually added to encourage readers, it often has the
opposite effect and may even appear condescending, especially when the reader
runs into trouble trying to apply the suggestions from the documentation. It is
almost always an improvement to simply drop the word from the sentence.
(there are more possible improvements like this, we can apply those in separate
PRs)
|
| | | |\ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Minor `lib.fileset` cleanups
|
| | | | | |/ / / /
| | | |/| | | |
| | | | | | | |
| | | | | | | | |
It's not very limited anymore :)
|
| |\| | | | | | | |
|
| | |\| | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* buildNpmPackage: allow nodejs to be passed as argument
* Update doc/languages-frameworks/javascript.section.md
Co-authored-by: Lily Foster <lily@lily.flowers>
---------
Co-authored-by: Lily Foster <lily@lily.flowers>
|
| |\| | | | | | | |
|
| | |\| | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Replaced with python3Packages except for the following to avoid misuse of pythonPackages
1. which we need for the explanation
2. which are replaced by python3Packages as variables
|
| | | |/ / / / / |
|
| |\| | | | | | |
|
| | |\| | | | | |
|