With this change, evaluating the `makeFlags` attribute does not result in building the referenced packages.
This makes it possible for users to override `buildInputs` and remove inputs they don't want without having to also make a modified copy of the `makeFlags` attribute.
An example use case is to remove the `jre` dependency.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/munin/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/.munin-check-wrapped -h’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/.munin-check-wrapped --help’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/.munin-check-wrapped help’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/munin-check -h’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/munin-check --help’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/munin-check help’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/.munin-cron-wrapped --help’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/munin-cron --help’ got 0 exit code
- ran ‘/nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37/bin/munin-node-configure help’ got 0 exit code
- found 2.0.37 with grep in /nix/store/af5ja0gxnyhdhg8qgfnfbvxdf7zl110c-munin-2.0.37
- directory tree listing: https://gist.github.com/44aa9c5969938bba7e7a4e9710568ae9
Add a new patch (adding_sconfdir_munin-node.patch) to be able to
configure the location of plugin-conf.d (otherwise it has to be
configured at build time). This patch is very similar to the
existing 'adding_servicedir_munin-node.patch'.
This continues #23374, which always kept around both attributes, by
always including both propagated files: `propgated-native-build-inputs`
and `propagated-build-inputs`. `nativePkgs` and `crossPkgs` are still
defined as before, however, so this change should only barely
observable.
This is an incremental step to fully keeping the dependencies separate
in all cases.
