| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
garble: 0.5.1 -> 0.6.0
|
|
|
|
writeCBin: fix formatting
|
|
|
|
Fix string context lost in `linkFarm`
|
|
Co-authored-by: pennae <82953136+pennae@users.noreply.github.com>
|
|
xivlauncher: init at 1.0.0.4
|
|
```nix
let pkgs = import ./. {}; in
pkgs.linkFarm "test" [
{ name = "foo"; path = ./README.md; }
]
```
The nix code above generates this result: (`nix build -f test.nix`)
```
lrwxrwxrwx 1 root root 31 Jan 1 1970 /nix/store/98mdz626n99w0467q4r203q154bnnli9-test/foo -> /home/juloo/w/nixpkgs/README.md
```
With this patch, the target file is naturally copied into the store:
```
lrwxrwxrwx 1 root root 53 Jan 1 1970 /nix/store/ndvffnardifqwzbp07g15llav55r5k1m-test/foo -> /nix/store/9rqwjskbbgbflrpyhzi6rak2j7jspr5f-README.md
```
|
|
Compressed firmware
|
|
This should be a significant disk space saving for most NixOS
installations. This method is a bit more complicated than doing it in
the postInstall for the firmware derivations, but this way it's
automatic, so each firmware package doesn't have to separately
implement its compression.
Currently, only xz compression is supported, but it's likely that
future versions of Linux will additionally support zstd, so I've
written the code in such a way that it would be very easy to implement
zstd compression for those kernels when they arrive, falling back to
xz for older (current) kernels.
I chose the highest possible level of compression (xz -9) because even
at this level, decompression time is negligible. Here's how long it took
to decompress every firmware file my laptop uses:
i915/kbl_dmc_ver1_04.bin 2ms
regulatory.db 4ms
regulatory.db.p7s 3ms
iwlwifi-7265D-29.ucode 62ms
9d71-GOOGLE-EVEMAX-0-tplg.bin 22ms
intel/dsp_fw_kbl.bin 65ms
dsp_lib_dsm_core_spt_release.bin 6ms
intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq 7ms
And since booting NixOS is a parallel process, it's unlikely (but
difficult to measure) that the time to user interaction was held up at
all by most of these.
Fixes (partially?) #148197
|
|
This reverts commit 7e589a45ef86abf9a6a737d9730925b81ee663b4.
|
|
The old logic flow had the structure
if ( … ) {
if ( … ) {
…
} else {
…
}
} else {
…
}
which is quite hard to follow in Nix. Instead we ensure that no if
expression is inside a then branch.
This change is zero rebuild, as no logic was changed.
|
|
- use propagatedBuildInputs to make sure ocaml plugin stuff is in path
- updated coqPackage.heq (broken url)
- fixed use of `DESTDIR` and `COQMF_COQLIB` in mkCoqDerivation
- adding `COQCORELIB` environement variable to put ocaml plugin files in the right place
- make metaFetch available from `coqPackages`
|
|
|
|
|
|
Already present in nixos/modules/testing/test-instrumentation.nix,
which is imported by the test framework.
|
|
|
|
And improve the test a bit, to assert correct wiring of `pkgs`.
|
|
|
|
https://github.com/NixOS/nixpkgs/commit/f8cc8ff5755528d9a73671481ba3d6fb00f4e8d5
fails to unset the variables in the environment due to a Bash quirk,
so set them to the empty string instead.
|
|
The generated C code contains large string literals that are longer than
the maximum length specified by the standard.
However, GCC has no trouble dealing with those strings, so we can just
add -Wno-overlength-strings.
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Woverlength-strings
|
|
|
|
|
|
|
|
|
|
|
|
makeInitrdNG: Strip more and remove output
|
|
Close #169965: the PR and real 'staging-next' branch contained
extra systemd rebuild that I wanted to avoid in this iteration.
(to save Hydra's work)
|
|
|
|
|
|
|
|
This parameter is being set to `$NIX_BUILD_CORES` by default. This is a
standard practice but there's a suspicion that this can produce broken
builds. For some details see
https://github.com/cargo2nix/cargo2nix/issues/184 . As a
work-around/test, it'd be good if codegen-units can be set to something
constant, such as `1`. This PR allows it.
Note that the default of `$NIX_BUILD_CORES` is preserved so this MR
causes no change in default behaviour and no rebuilds.
|
|
This strips all elf files as far as possible and removes a lot of
unnecessary output. Also wrap in the binaries instead of relying on
$PATH.
|
|
|
|
|
|
|
|
|
|
Previously buildDotnetModule did not properly inherit some arguments from
derivations, take for example this expression:
dotnetFlags = [
"--runtime linux-x64"
];
It would error out as follows: "MSBUILD : error MSB1001: Unknown switch.".
Setting the same flag from bash would work fine. This fixes that, all
arguments should now be properly interpreted :)
|
|
There used to be a few issues with the way we generate the nuget source:
* The derivation generated for the deps would have "nuget-deps" in them twice:
/nix/store/...-foo-1.0-nuget-deps-nuget-deps
* We always tried to generate the dependencies for "projectReferences"
even when it wasn't set, causing a warning.
This fixes those issues :)
|
|
This improves the metadata generation, previously it would take any
"license" entry from the nuspec, and tried to match it to an spdx ID from
"lib.licenses".
Sometimes however licenses are provided in plain-text, which we
obviously cannot cleanly resolve. This resulted in in useless information
("LICENSE.txt") being written to "meta.license".
|
|
|
|
|
|
|
|
darwin for security-framework-sys
|
|
|
|
Prevent the wrapper from being affected by the derivation's CFLAGS,
which may not even apply to GCC.
|
|
Reduces the likelihood of having apps wrapped twice by a shell script,
which causes problems with argv0.
|
|
|
|
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
|
