| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| |
| | |
I came this commit hash to terwiz[m] on IRC, who is trying to figure out
what the last version of Spectrum that worked on their NUC with Nvidia
graphics is.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
targetPlatform is the platform the current package's programs will
produce binaries for — only relevant for compilers and
similar. hostPlatform is the platform the current package's programs
will run on.
The incorrect use of targetPlatform meant that anything that tried to
link to it (like cryptsetup) would fail to build when it was used as a
native build input for a cross-compiled Musl derivation.
|
| |
| |
| |
| | |
Reduces the closure size of pkgsStatic.kmod from 51.0M to 541.6K.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
generate-config.pl's auto modules feature answers "m" to any Kconfig
question it thinks supports being a module. It detected this by
seeing if the help shown by make config (called "alts" by the script)
contained the string "/m", which it would in the case of e.g a
tristate option, where alts would be "N/m/y/?".
But then along came CONFIG_MODPROBE_PATH in Linux 5.13, with a default
value, shown in the make config help, of "/sbin/modprobe".
generate-config.pl would see the "/m" substring, and answer "m" to the
question, meaning (I think) that the built kernel would expect the
modprobe binary to be at /m. This broke the (non-NixOS) VM images I
build with Nix. NixOS was unaffected because it uses a different
mechanism to set the modprobe path.
With the current architecture, we can't 100% determine whether a
Kconfig option is a string or a tristate, but we can get a lot closer
by using a better regex. My new regex only accepts single word
characters, separated by slashes, with a "/?" at the end. This is
much less likely to ever end up as the default value of a string
option.
Tested by building linux_latest.configfile before and after my
changes, and checking the only difference is the correct default for
CONFIG_MODPROBE_PATH.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We don't currently have any software in Nixpkgs that uses Meson's Rust
support that I could find (rather than just shelling out to Cargo from
Meson), but it's easy to test this works regardless, e.g. with the
following which uses Meson's built-in template for a Rust project.
stdenv.mkDerivation {
name = "rust-test";
unpackPhase = ''
mkdir src
cd src
meson init -l rust
'';
nativeBuildInputs = [ meson ninja rustc ];
}
|
| |
| |
| |
| |
| |
| |
| | |
Since Meson isn't part of stdenv, it doesn't really make sense for
stdenv to handle mesonFlags. And putting it in stdenv imposes some
limitations — we can't depend on e.g. rust.toRustTargetSpec, which
we'll need to introduce Rust support in the cross file.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some use cases (think appliances) call for veritysetup but not
cryptsetup, and others (like NixOS) don't need veritysetup and usually
not integritysetup. This is especially useful for pkgsStatic where
each program contains a whole copy of the libraries it needs so is
quite large.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reduces closure sizes by making the libraries not depend on the
binaries, which is good for static builds, and (when statically
linked) making the binaries not depend on the libraries, which is good
for static builds.
When static building, we additionally have to disable loading LUKS
plugins from $lib to avoid a reference, which probably wouldn't have
worked anyway.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, the "out" output of openssl would contain would contain a
couple of tiny libraries in etc/, and the big OpenSSL libraries in
lib/. This bloated closures when building things against OpenSSL with
pkgsStatic. To fix this, introduce a lib output, so only the config
files are left in out.
Additionally, we have to disable support for dynamic engines in static
builds to avoid a reference to the engines directory in $lib. I don't
think it's likely that this would ever have worked anyway.
|
| |
| |
| |
| |
| |
| |
| | |
For systems without internet connections, it doesn't make sense to
require the existence of an /etc/resolv.conf file to disable
resolvconf, so let's expose networking.resolveconf.enable as a public
option that can be set to false.
|
| | |
|
| |
| |
| |
| |
| |
| | |
What if $out is a file?
WIP: add a release note since this is breaking, and check uses in nixpkgs
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This is the same fork now used by Alpine, Arch, Debian, Gentoo, and
SliTaz. vpnc-script is no longer bundled, but we already have it
packaged anyway so that's okay.
|
| |
| |
| |
| |
| | |
I think "CLI" is a very strange name for this, but that's what
upstream calls it.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| | |
| | | |
ci: add warning to actions with writeable GITHUB_TOKEN
|
| | |
| | |
| | |
| | | |
Co-authored-by: ckie <25263210+ckiee@users.noreply.github.com>
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
r-ryantm/auto-update/python3.10-youtube-search-python
python310Packages.youtube-search-python: 1.6.2 -> 1.6.3
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
python3Packages.myfitnesspal: add toPythonApplication
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
python3Packages.slixmpp: 1.8.0.1 -> 1.8.1
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes the build with Linux 5.17.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
furnace: 0.5.6 -> 0.5.8
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | | |_|_|_|/
| | |/| | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
minio-certgen: 1.1.0 -> 1.2.0
|
| | | |_|_|_|/
| | |/| | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
skaffold: 1.36.0 -> 1.37.0
|
| | |/ / / / / |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
distrobox: 1.2.13 -> 1.2.14
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
squashfsTools: 4.5 -> 4.5.1
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The patch that was previously fetched from GitHub is now part of the
4.5.1 release, and is no longer needed. Furthermore, 4.5.1 introduces
some new scripts to build manpages, and some new build inputs are
required to make that work.
This also rebases the Darwin patch. I don't have a Mac so I can't test
this personally. There was one conflict:
diff --cc squashfs-tools/read_xattrs.c
index 2067f80,b28c3a0..0000000
--- a/squashfs-tools/read_xattrs.c
+++ b/squashfs-tools/read_xattrs.c
@@@ -36,9 -38,7 +38,7 @@@
#include "xattr.h"
#include "error.h"
- #include <stdlib.h>
-
-extern int read_fs_bytes(int, long long, int, void *);
+extern int read_fs_bytes(int, long long, long long, void *);
extern int read_block(int, long long, long long *, int, void *);
static struct hash_entry {
Resolved by updating the signature from int to long long.
|
| |\ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
r-ryantm/auto-update/opentelemetry-collector-contrib
opentelemetry-collector-contrib: 0.46.0 -> 0.47.0
|
| | | | | | | | | | |
|