pkgs/development/interpreters · nixpkgs · Tangled

What happens if I push all of nixpkgs

nixpkgs pkgs development interpreters

31 folders

at staging-next

K900 · Merge remote-tracking branch 'origin/master' into staging-next · 1y ago

acl2: 8.5 -> 8.6 and mark darwin builds as compatible

treewide: format all inactive Nix files

babashka-unwrapped: 1.12.207 -> 1.12.208

treewide: run nixfmt 1.0.0

treewide: run nixfmt 1.0.0

treewide(java-users): clean callPackage overrides, by-name some (#443954)

treewide: format all inactive Nix files

treewide: run nixfmt 1.0.0

beamPackages.elixir: avoid throwing for incompatibility in CI

emilua: 0.11.6 -> 0.11.7

erlang_29: 28.0.4 -> 28.1

falcon: unstable-2018-10-23 -> 0-unstable-2023-11-19

various: remove superflous usages of pname

gnudatalanguage

treewide: run nixfmt 1.0.0

guile: disable stripping on `linux` as well (`binutils-2.45` compat)

various: remove superflous usages of pname

jruby: 9.4.12.0 -> 10.0.0.0

treewide: remove usage of deprecated apple_sdk framework stubs

treewide: run nixfmt 1.0.0

love2d: add Darwin platform support

top-level/release-attrpaths-superset: remove __attrsFailEvaluation (#428015)

treewide: run nixfmt 1.0.0

treewide: run nixfmt 1.0.0

perl: fix build when cross-compiling to the musl libc (#430413)

php: move $out/lib/build used by phpize to dev output

pypy3: 7.3.19 -> 7.3.20 (#443765)

treewide: run nixfmt 1.0.0

ruby: remove `fetchFromSavannah` fetcher with files from autoconf

spidermonkey_140: 140.3.0 -> 140.3.1

supercollider: disable vulnerable qtwebengine by default

Merge branch 'staging-next' into staging