| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\ \ \ \ \ |
|
| | |\ \ \ \ \ |
|
| | | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The nixpkgs documentation mentions how to update out of tree plugins but
one problem is that it requires a nixpkgs clone.
This makes it more convenient.
I've had the need to generate vim plugins and lua overlays for other
projects unrelated to nix and this will make updates easier (aka just
run `nix run nixpkgs#vimPluginsUpdater -- --proc=1` or with the legacy commands:
`nix-shell -p vimPluginsUpdater --run vim-plugins-updater`.
I added an optional "nixpkgs" argument to command line parser, which is the path
towards a nixpkgs checkout. By default the current folder.
update-luarocks-packages: format with black
|
| |\| | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit adds minimal documentation of the supported platforms.
More exhaustive documentation would require producing a list of
platforms for each of the 7 tiers. This was attempted in #245368, but it
quickly became clear that that would be a long-term effort.
In the meantime, this commit adds the most important information to the
manual.
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* nixpkgs manual: add an alternative example in stdenv-separateDebugInfo
This change gets rid of the indirect reference to `nix-env -i` usage
and shows how to achieve the same goal with a shell expression.
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |\| | | | |
|
| | | | | | |
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
the `from2Nix` suffix is a legacy from vim2nix but we dont use that anymore. It makes the name of the function unusual and long.
|
| | | | | |
| | | | |
| | | | | |
`-z bindnow` doesn't exist. The actual flag added is `-z now`.
|
| |\| | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The text was originally added [0] following an apparently incomplete
research on how everything plays together. In fact, Nix propagates
`outputs` to the corresponding nested derivations, and there is some
messy behavior in Nixpkgs that only seems to propagate
`meta.outputsToInstall` in `buildEnv`[1].
This change moves the hints on how to use NixOS specifics to NixOS
module documentation (which is hopefully easier to find through
search.nixos.org), describes the default behavior in Nixpkgs (updating
a the link to the source), and removes the confusing mention of
`nix-env`.
the last of them should not be there to begin with. we don't want
beginners to use `nix-env`, as this is known to run them into trouble
eventually.
[0]: https://github.com/NixOS/nixpkgs/pull/76794
[1]: https://github.com/NixOS/nixpkgs/blob/1774d07242995050d2d8a91cb4da0855eac2e472/pkgs/build-support/buildenv/default.nix#L66
|
| | |\ \ \ \
| | | | | |
| | | | | | |
python3Packages.flitBuildHook: remove
|
| | | | | | | |
|
| |\| | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
* nixpkgs manual: doc python: add hyperlinks to Python section
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |\| | | | |
|
| | | | | | |
|
| |\| | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
`lib.fileset.union`, `lib.fileset.unions`: init
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also some minor formatting improvements
|
| |\| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Co-authored-by: Sandro Jaeckel <sandro.jaeckel@gmail.com>
|
| | | |_|/ /
| |/| | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
rewrite `runCommand` interface docs
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
specifically this corrects the misleading statement that `env` takes
environment variables for the derivation.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
(#255131)
* BEAM docs: recommend `nix-shell -p` and `shell.nix` instead of `nix-env`
Co-authored-by: asymmetric <lorenzo@mailbox.org>
|
| |\ \ \
| | | |
| | | | |
ruby: document extraConfigPaths option from bundlerEnv
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Otherwise the fetcher is unuseable with patches
whose filename (in Debian) doesn't end in `.patch`.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
python310Packages.buildPythonPackage: introduce pyproject option
|
| | | |_|/ /
| |/| | | |
|
| | | | | |
| | | | |
| | | | | |
The Nixpkgs license is pure MIT.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Instead of just telling the reader to go find the relevant section of the Nix
manual, let's just link to it. Yay hypertext!
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Updates meta.chapter.md with a reference link to the usage of the package description field instead of referring to nix-env
---------
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
| |\ \ \ \
| | | | |
| | | | | |
php: add new Composer builder
|
| | | |/ /
| |/| | |
|
| |\| | | |
|
| | |/ / |
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Clarify that the monochrome font is not included, per #221181.
The new name is also coherent with the name of the font,
according to `fontconfig`: Noto Color Emoji.
|
| |\| | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
- Normalize header IDs, in order to not cause conflicts with identically named
headers in other docs.
- Reorganize the hierarchy of information.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
- Normalize header IDs, in order to not cause conflicts with identically named
headers in other docs.
- Reorganize the hierarchy of information.
|