| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
* Add test case for include dir
* buildRustCrate: replace hyphen with underscore in env
This fixes a bug that prevents encoding_c from building.
|
| |\
| |
| | |
dockerTools: fix skopeo commands
|
| | | |
|
| |/ |
|
| | |
|
| |\
| |
| | |
dockerTools: Properly add /nix/ and /nix/store/ first to layer.tar
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In https://github.com/NixOS/nixpkgs/pull/58431 the authors ensured that
the resulting layer.tar would always list
/nix/
/nix/store/
first to fully comply to the tar spec. Various refactorings later it is only
ensured to create /nix/ but NOT /nix/store anymore. Instead tar transformed
them to /nix/nix and /nix/nix/store.
|
| |\ \
| | |
| | | |
gdc: init at 9.3.0
|
| | |/ |
|
| |/ |
|
| |\
| |
| | |
Some performance optimizations to dockerTools.build{,Layered}Image
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Calculating the tarsum after creating a layer is inefficient, since
we have to read the tarball we've just written from the disk.
This commit simultaneously calculates the tarsum while creating the
tarball.
|
| | |
| |
| |
| |
| |
| |
| | |
Appending to an existing tar archive repeatedly seems to be a quadratic
operation, since tar seems to traverse the existing archive even using
the `-r, --append` flag. This commit avoids that by passing the list of
files to a single tar invocation.
|
| | | |
|
| |\ \
| | |
| | | |
dockerTools.examples: fix the nginx image
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Nginx now requires directories `/var/log/nginx` and `/var/cache/nginx`
to be existing.
The objective is to fix the test `nixosTests.docker-tools`.
|
| |\ \ \
| | | |
| | | | |
Preserve environment variables from the parent image on dockerTools.buildImage
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | | |
Agda rework
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
build-bazel-package: switch hash mode to “flat”
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
flat hashes can be substituted through hashed-mirrors, while recursive
hashes can’t. This is especially important for Bazel since the bazel
fetch dependencies can come from multiple different methods (git,
http, ftp, etc.). To do this, we create tar archives from the
output/external directory, which is then extracted to build. All of
the Bazel hashes are all updated.
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some PECLs depend on other PECLs and, like internal PHP extension
dependencies, need to be loaded in the correct order. This makes this
possible by adding the argument "peclDeps" to buildPecl, which adds
the extension to buildInputs and is treated the same way as
internalDeps when the extension config is generated.
|
| |\| | | |
|
| | |\ \ \
| | | |/
| | |/| |
|
| | | |\ \
| | | | |
| | | | | |
fetchurl: don’t run ‘postFetch’ on hashed-mirrors
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
hashed-mirrors are content addressed. So if $outputHash is in the
hashed-mirror, changes from ‘postFetch’ would already be made. So,
running postFetch will end up applying the change /again/, which we
don’t want.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
tarballs.nixos.org is omitted from the change because urls from there
are always hashed and checked
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is analogous to buildImageWithNixDb but instead uses
buildLayeredImage under the hood.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If a user provides `nativeBuildInputs = [ llvmPackages.bintools ]` or any other
package containing a `${prefix}/bin/diff`, the builder could use it instead
of the standard unix `diff`, causing a build failure.
This updates the call to specify an abspath to `diff` and avoid reliance on `PATH`.
Resolves #87081
|
| |\| | | |
|
| | | | | |
|
| |\| | | |
|
| | | | |
| | | |
| | | |
| | | | |
dune allows to specify the number of jobs to build the package.
|
| |\ \ \ \
| |/ / /
|/| | | |
darwin.binutils: propagate man pages from darwin.cctools
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Otheriwse running the tool fails with
line 41: jq: command not found
|
| |\ \ \ \
| | | | |
| | | | | |
srcOnly: fix invocation and document
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The only reason to pass build inputs is to extend the unpackPhase with
custom unpack commands. Eg: add "unrar" to unpack rar sources. And those
should really be passed as native build inputs. Why? Because
nativeBuildInputs is for dependencies that are used at build time but
will not propagate as runtime dependencies. And also, cross-compilation.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously, callPackage would try and fill the arguments such as `name`
and `src` which would cause problems if those existed as top-level
attributes. This also makes it clearer what part is the function
signature.
Then document the derivation inline in the code to explain the ellipsis
and various use-cases.
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
lapack: fix darwin library identifiers
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The build system already sets these properly to the absolute path so no
need to patch the libraries on darwin.
$ otool -D result/lib/liblapacke.dylib
result/lib/liblapacke.dylib:
/nix/store/k88gy5s765yn3dc5ws3jbykyvklm7z96-openblas-0.3.8/lib/libopenblasp-r0.3.8.dylib
Fixes #85713
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
This then supports using functions like writeShellScriptBin with script names
that would be invalid as derivation names
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | |_|/ /
| |/| | | |
BLAS/LAPACK fixup and expand docs
|
| | | | | |
| | | | |
| | | | |
| | | | | |
To match the soname, we need to use libblas.so.3, liblapack.so.3.
|