| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
treewide: use runtimeShell instead of stdenv.shell whenever possible
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
|
| |/
|
| |
Add missing verb.
|
| |\
| |
| | |
appimageTools: init
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The appimageTools attrset contains utilities to prevent
the usage of appimage-run to package AppImages, like done/attempted
in #49370 and #53156.
This has the advantage of allowing for per-package environment changes,
and extracts into the store instead of the users home directory.
The package list was extracted into appimageTools to prevent
duplication.
|
| | |
| |
| | |
closes siers/nix-gitignore#6
|
| |\ \
| | |
| | | |
random cleanups and a tiny fix
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Fix manual Makefile by including function doc generation
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since #53055 was merged the Makefile for the manual could not be run
correctly as the generated function documentation was included, but
not actually generated.
This adds the necessary generation step by first building the XML file
containing function locations and preserving its store path in a
variable, which is then used both for linking of the locations file
and as a build input for the function docs generator.
This fixes #55014
|
| |\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Comments on conflicts:
- llvm: d6f401e1 vs. 469ecc70 - docs for 6 and 7 say the default is
to build all targets, so we should be fine
- some pypi hashes: they were equivalent, just base16 vs. base32
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Mostly taken from requested changes exactly as recommended.
|
| | | |
| | |
| | |
| | | |
Fixes #25507.
|
| | | |
| | |
| | |
| | | |
Fixes #34857.
|
| | |/
| |
| |
| | |
Fixes #32439.
|
| | |\
| | |
| | | |
doc: don't overwrite makeFlagsArray in the example
|
| | | |
| | |
| | |
| | |
| | | |
Arrays like these should be appended to instead of overwritten in almost
every case to avoid loosing the existing flags.
|
| | |\ \
| | | |
| | | | |
prefer-fetch-remote: an overlay to fetch on remote builders
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is useful when running tools like NixOps or nix-review
on workstations where the upload to the builder is significantly
slower then downloading the source on the builder itself.
|
| |\| | | |
|
| | |\ \ \
| | | | |
| | | | | |
manual: limit text width
|
| | | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Currently the manual scales to the view port of the browser.
This leads to an unreadable layout and I found myself
reading the xml source instead.
The optimal width would be around 50 characters per line.
Since we have code listings also in the manual I relaxed
this limit a bit towards 70 characters per line.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This appears to much more widely used in the nixpkgs documentation.
Also not all contributors are he's.
|
| |\| | | |
|
| | |\ \ \
| | |_|/
| |/| | |
manual: document ways of obtaining source hashes
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
... and security nuances
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We can't run the checkPhase when build != host, so we may as well make
the checkInputs native.
This signicantly improves the situation of Python packages when enabling
strictDeps.
|
| |\ \ \ \
| |/ / /
|/| | | |
See the motivation in fd97db43bcb05e37f6bb77f363f1e1e239d9de53 (#41819).
|
| | | | | |
|
| |\ \ \ \
| |_|_|/
|/| | | |
neovim-qt: wrap in separate derivation
|
| | | | | |
|
| |\ \ \ \
| | |_|/
| |/| | |
|
| | |\ \ \
| | | | |
| | | | | |
Elm: automate packaging with elm2nix
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
- rewrite documentation
- automate whole process into update.sh
- remove all legacy snippets
|
| |\| | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Modifies the build process of the manual to invoke nixdoc
automatically to generate XML files with function documentation.
Currently documentation is present for five of the files in `lib/`.
To add another file to the generated docs, both
`doc/functions/library.xml` and `doc/lib-function-docs.nix` must be
updated.
|
| |\| | |
|
| | |\ \
| | | |
| | | | |
Fix vim-plugin dependencies
|
| | | | |
| | | |
| | | |
| | | | |
nativeImpl previously simply ignored dependency information.
|
| |\| | | |
|
| | |\ \ \
| | |/ /
| |/| | |
Mobile updates
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since Intel's default openmp implementation is available in the same src
tarball, we can just include it in the package. This means that `mkl` now "just
works" without any environment variables, fragile setup-hooks, or forced
propagation.
Since the openmp implementation is only needed at runtime (and for test cases),
users can substitute a different one if they prefer by exporting it with
`LD_PRELOAD`, which is how Intel recommends handling this. If they do not do so,
`libiomp.so` lives next to `libmkl_rt.so` and thus will be in the RPATH as a
sane default.
Since this still comes from the same src tarball, we can ship it without losing
the fixed-output derivation; likewise, since Hydra is not building or caching
these, shipping these proprietary packages costs no bandwidth for the nix
community.
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|