| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
buildFHSEnvBubblewrap: allow more varied $DISPLAY syntax
|
|
|
|
|
|
|
|
|
|
testers.hasPkgConfigModules: fix bug in `versionCheck` handling
|
|
There should be no reason to use env here:
1. In places where it is used to run dotnet with environment variables,
the same can be done with shell syntax.
For example, `env "FOO=$bar" baz` is equivalent to `FOO="$bar" baz`.
2. Otherwise, it just unnecessarily forces PATH lookup for dotnet
command. In addition to that, some dotnet invocations did not use
env.
|
|
I decided to avoid the use of `buildComposerProject because it requires `composer-local-repo-plugin` which is going to be refactored.
|
|
|
|
|
|
--frozen is stricter than we need in Nixpkgs. If a Cargo.lock is
slightly wrong, or (in my use case) if building a subproject that is
not a member of the top-level workspace, but the correct Cargo.lock
can be entirely resolved from the existing top-level Cargo.lock, it
should be deterministic, and shouldn't cause any problems, to let
cargo generate the new Cargo.lock. This should result in less need to
bother upstreams about fixing their Cargo.lock files in cases where
they could have been automatically fixed.
|
|
Adding cc to propagatedBuildInputs makes derivations with
makeBinaryWrapper in nativeBuildInputs run the cc-wrapper
setup hook. This isn't an issue for derivations using
stdenv, as the cc setup hook is already run by default.
However, derivations that are made with stdenvNoCC, e.g.
because they're made with runCommand, will not run the
cc-wrapper setup hook without this change.
For some reason the FreeBSD native compiler will not work
correctly without the setup hook.
|
|
This doesn't change anything to the existing workflow
|
|
The $DISPLAY variable has a format of [host]:num[.screen]. Previously,
the number would only be extracted properly if it had the form :num.
Allow all forms but correctly discard the unused parts.
|
|
|
|
treewide: remove `multiArch=false` and wrong usage of `extraPkgs`
|
|
Sane default in preparation for the next commit.
|
|
buildsupport/php: add passthru.updateScript
|
|
mismatches
|
|
|
|
Broke tests, as the version check was effectively always enabled:
https://github.com/NixOS/nixpkgs/pull/307770#issuecomment-2102586718
|
|
Shell script is currently buggy and effectively ignores the value, always enforcing version match:
https://github.com/NixOS/nixpkgs/pull/307770#issuecomment-2102586718
|
|
|
|
build-support/meson: explicitly use ambiant CMake during cross compilation
|
|
|
|
Thanks to Qyriad, it was found out that Nixpkgs was unable to cross
compile when CMake was needed at cross compilation time with Meson
because Meson refuse to use the ambiant CMake.
A simple fix is to always provide the ambiant CMake and trust the
packager to pass the right CMake, otherwise the rest of the build would
probably fail in mysterious ways.
An example of package that required this fix is the Lix, a Nix
implementation, that uses `toml11` discovered via CMake during the Meson
configure phase.
Co-authored-by: Qyriad <qyriad@qyriad.me>
Signed-off-by: Raito Bezarius <masterancpp@gmail.com>
|
|
; Conflicts:
; maintainers/scripts/luarocks-packages.csv
; pkgs/development/lua-modules/generated-packages.nix
|
|
This fixes at least one bug with default-features, and also
just aligns us more with what Cargo actually does.
Also some Python style fixes and a bit less mutating state.
|
|
buildRustPackage: add new supported platforms
|
|
The new NetBSD platforms have appeared since last time I updated this
list, but it looks like I just missed the MIPS linux ones last time.
|
|
PHP packages where upstream provides a lock file can be automatically updated with the standard updateScript
|
|
|
|
dub-to-nix,buildDubPackage: allow git-type dependencies
|
|
linux kernel: prefer zstd where possible
|
|
|
|
|
|
Pave the way for having multiple versions in the future
|
|
|
|
dotnet: fix dotnet executables in darwin sandbox
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts in luaPackages.luarocks-nix:
- 8b563cd9f923cdf009b3864a358d912103703320 switched to the new version format (prefixed by 0 since there was no relevant last tag in the branch).
bc4f6fa54321533b250984f7b3813f8d343dfde1 bumped version and switched to the new version format. But the tag used is not part of the branch the commit comes from (master).
Used the new version but replaced the tag prefix with 0.
- b73ec84b9eed8de7e9095e779ee3d4066ceb091e removed meta (it is already set in the overridden luarocks). But that would cause the update script to try to update the overridden luarocks (as did the previously used old.meta).
bf311d950e4c5d65fae66717c7c3d4f085ff6415 modified meta to fix the update script properly.
Kept the meta from the latter since it allows update script to work.
|
|
This fixes:
Could not load ICU data. UErrorCode: 2
We're using a hook instead of a wrapper because various things like to
reference the unwrapped dotnet executable.
|
|
|
