Bazel is a build tool, much like Make and many others. Like Make, it
should be agnostic to the compiler toolchains the user brings into
scope. Bazel has special rules that encode domain specific knowledge
for how to compile a C++ program, or indeed a Java program and a few
others. But that's not to say that at runtime Bazel should assume
a specific C++ compiler or Java compiler anymore than Make does.
The main impact of this change is that packages that build with Bazel
will have to list the compilers they want in their `buildInputs` or
similar, rather than relying on the `bazel` package pulling them in
transitively.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/conan/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5/bin/.conan_server-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5/bin/conan_server had a zero exit code or showed the expected version
- /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5/bin/.conan_build_info-wrapped passed the binary check.
- /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5/bin/conan_build_info passed the binary check.
- Warning: no invocation of /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5/bin/.conan-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5/bin/conan had a zero exit code or showed the expected version
- 2 of 6 passed binary check by having a zero exit code.
- 0 of 6 passed binary check by having the new version present in output.
- found 1.4.5 with grep in /nix/store/gid7f7w71lbiissjcbjsjvlxhmix6i94-conan-1.4.5
- directory tree listing: https://gist.github.com/25fd7dbaab3b2c2b870221856de5199b
- du listing: https://gist.github.com/b94750efe01cb63b9541d4b897485f62
In particular, this contains Firefox-related and libgcrypt updates.
Other larger rebuilds would apparently need lots of time to catch up
on Hydra, due to nontrivial rebuilds in other branches than staging.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/conan/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4/bin/.conan_server-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4/bin/conan_server had a zero exit code or showed the expected version
- /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4/bin/.conan_build_info-wrapped passed the binary check.
- /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4/bin/conan_build_info passed the binary check.
- Warning: no invocation of /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4/bin/.conan-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4/bin/conan had a zero exit code or showed the expected version
- 2 of 6 passed binary check by having a zero exit code.
- 0 of 6 passed binary check by having the new version present in output.
- found 1.4.4 with grep in /nix/store/pdza6q7n1rywgra2022zvbi05fj47kjy-conan-1.4.4
- directory tree listing: https://gist.github.com/0da299922c958da51520fdd195a2d369
- du listing: https://gist.github.com/7e5d6a9b06f35b233151c026f6dd089b
When dontUseCmakeBuildDir is true (aka the default), it overrides
cmakeDir regardless of the package configuration.
While packaging netbee, I needed to both keep dontUseCmakeBuildDir to
true (some hardcoded paths expect the build folder) and set cmakeDir
(since CMakeList.txt was in a subfolder) which proved impossible.
Here is the fix.
Lots of packages are missing versions in their name. This adds them
where appropriate. These were found with this command:
$ nix-env -qa -f. | grep -v '\-[0-9A-Za-z.-_+]*$' | grep -v '^hook$'
See issue #41007.
