Upstream is concatenating CMAKE_INSTALL_LIBDIR onto CMAKE_INSTALL_PREFIX to get
a directory to use for the install_name on Darwin. This is not the right way of
making CMAKE_INSTALL_LIBDIR absolute.
The config was first set up for breakage when the CMAKE_INSTALL_LIBDIR was made relative,
in order to work around the wrong concatenation. This caused the _IMPORT_PREFIX to be
computed by walking up the directory tree from the config file, instead of using
the absolute CMAKE_INSTALL_LIBDIR.
Then outputs were introduced to the derivation and the config was moved to a different
output. Now the prefix it walks up to is the wrong prefix, and the config is busted.
Fix by reverting the original workaround so we have an absolute CMAKE_INSTALL_LIBDIR,
and pulling a patch that fixes the bad concatenation.
* FluidSynth 1.1.11 was kept around as a dependency of some packages
that hadn't yet adjusted to API breakages. All of these packages now
use FluidSynth 2.x, so fluidsynth_1 can be removed. It has been broken
ever since glib was updated to 2.70 and was affected by an unpatched
CVE.
* Refactor expression a bit, use pname instead of name.
* Add changelog entry in case someone was using this downstream
(accidentally?).
Fixes#141508.
Fixes#124624.
continuation of #109595
pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.
python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth -h` got 0 exit code
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth --help` got 0 exit code
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth help` got 0 exit code
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth -V` and found version 1.1.10
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth -v` and found version 1.1.10
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth --version` and found version 1.1.10
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth version` and found version 1.1.10
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth -h` and found version 1.1.10
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth --help` and found version 1.1.10
- ran `/nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10/bin/fluidsynth help` and found version 1.1.10
- found 1.1.10 with grep in /nix/store/23kh3gax6a023mi2r3q31fd1mixa1k14-fluidsynth-1.1.10
- directory tree listing: https://gist.github.com/fbd821b325f18bdbc65812caeb1e0ecc
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9/bin/fluidsynth -h` got 0 exit code
- ran `/nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9/bin/fluidsynth --help` got 0 exit code
- ran `/nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9/bin/fluidsynth -V` and found version 1.1.9
- ran `/nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9/bin/fluidsynth --version` and found version 1.1.9
- ran `/nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9/bin/fluidsynth -h` and found version 1.1.9
- ran `/nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9/bin/fluidsynth --help` and found version 1.1.9
- found 1.1.9 with grep in /nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9
- found 1.1.9 in filename of file in /nix/store/lahkxc281j7vxzivbp68c71k6jgjzmcj-fluidsynth-1.1.9
Currently, we have a 'jack' package with attrname 'jack1d' and a
'jackdbus' package with attrname 'jackaudio'. Make it consistent 'jack1'
and 'jack2' in both package name and attrname.
This aligns the naming with what can be found on the JACK homepage.
Q: what's the difference between jack1 and jack2?
A: http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2
