Darwin machines come with a case-insensitive filesystem by default. The
gflags package's source contains a file 'BUILD' and the build process
attempts to create a directory called 'build', which fails on
case-insensitive filesystems.
Add a prePatch hook to rename the BUILD file (which is for use with an
unrelated build tool) to something that doesn't conflict with the
'build' directory. This hook allows this derivation to be built on
case-insensitive filesystems.
Add metadata to the derivation because previously it had none.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/libvisio/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2raw --version` and found version 0.1.6
- ran `/nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2raw --version` and found version 0.1.6
- ran `/nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2xhtml --version` and found version 0.1.6
- ran `/nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2xhtml --version` and found version 0.1.6
- ran `/nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vsd2text --version` and found version 0.1.6
- ran `/nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6/bin/vss2text --version` and found version 0.1.6
- found 0.1.6 with grep in /nix/store/bm8rhp6ljq7n0iqhpn4f1j3p013ps704-libvisio-0.1.6
- directory tree listing: https://gist.github.com/a7d83a73b3560d8cfa739ca582d98dcd
Manually cleaned up & split outputs.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 113.00.00 with grep in /nix/store/rpbwnyaisfm27cf36hb7scsa833r1lkb-ocaml-pa_ounit-113.00.00
- directory tree listing: https://gist.github.com/7284ca806fd00f73984a14b088879e92
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 113.00.02 with grep in /nix/store/ph9bs0vwwgpm1gcypd37ia7h3iybrzlf-ocaml-type_conv-113.00.02
- directory tree listing: https://gist.github.com/e0e5582781203fe8077a8ede54af0ef6
This is required by some included addons (such as ANT landscape). Note
that we can't use -DWITH_PYTHON_INSTALL_NUMPY=ON because it's
conditional on -DWITH_PYTHON_INSTALL=ON.
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/freecell-solver/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/fc-solve -h` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/fc-solve --help` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/fc-solve --version` and found version 4.18.0
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/pi-make-microsoft-freecell-board -h` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/pi-make-microsoft-freecell-board --help` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/pi-make-microsoft-freecell-board help` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/fc_solve_find_index_s2ints.py -h` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/fc_solve_find_index_s2ints.py --help` got 0 exit code
- ran `/nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0/bin/fc_solve_find_index_s2ints.py help` got 0 exit code
- found 4.18.0 with grep in /nix/store/k186rg37jwk63hvw2h1nmpmssa3cwrj4-freecell-solver-4.18.0
- directory tree listing: https://gist.github.com/2c22e8a4355b2da3c90bfde6c8d92c13
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/mbuffer/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/sjlbs2k9114xlxalqcz2n0jj90lvik07-mbuffer-20180318/bin/mbuffer -h` got 0 exit code
- ran `/nix/store/sjlbs2k9114xlxalqcz2n0jj90lvik07-mbuffer-20180318/bin/mbuffer --help` got 0 exit code
- ran `/nix/store/sjlbs2k9114xlxalqcz2n0jj90lvik07-mbuffer-20180318/bin/mbuffer -V` and found version 20180318
- ran `/nix/store/sjlbs2k9114xlxalqcz2n0jj90lvik07-mbuffer-20180318/bin/mbuffer --version` and found version 20180318
- found 20180318 with grep in /nix/store/sjlbs2k9114xlxalqcz2n0jj90lvik07-mbuffer-20180318
- directory tree listing: https://gist.github.com/5b88f842903984d6134c96d89c2169de
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/freeciv-gtk/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server -h` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server --help` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server help` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server -V` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server -v` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server --version` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server version` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server -h` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server --help` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-server help` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-gtk2 -h` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-gtk2 --help` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-gtk2 -v` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-gtk2 --version` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-manual -h` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-manual --help` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-manual -v` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-manual --version` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-mp-gtk2 -h` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-mp-gtk2 --help` got 0 exit code
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-mp-gtk2 -v` and found version 2.5.11
- ran `/nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11/bin/freeciv-mp-gtk2 --version` and found version 2.5.11
- found 2.5.11 with grep in /nix/store/h5yjw60axfcj1qiva25shmxdh0b4h6xy-freeciv-gtk-2.5.11
- directory tree listing: https://gist.github.com/02a6a0c73fce1c016f7e3dc7111c76b3
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/hpx/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/xg48bc9gkcq2hyk51hxy5s7x8l0s70r9-hpx-1.1.0/bin/hpxrun.py -h` got 0 exit code
- ran `/nix/store/xg48bc9gkcq2hyk51hxy5s7x8l0s70r9-hpx-1.1.0/bin/hpxrun.py --help` got 0 exit code
- found 1.1.0 with grep in /nix/store/xg48bc9gkcq2hyk51hxy5s7x8l0s70r9-hpx-1.1.0
- found 1.1.0 in filename of file in /nix/store/xg48bc9gkcq2hyk51hxy5s7x8l0s70r9-hpx-1.1.0
- directory tree listing: https://gist.github.com/377d8c673231332bb40acb55fed39e53
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/supercollider/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/scsynth -v` and found version 3.9.2
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/supernova -h` got 0 exit code
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/supernova --help` got 0 exit code
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/supernova -v` and found version 3.9.2
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/supernova --version` and found version 3.9.2
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/sclang -h` got 0 exit code
- ran `/nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2/bin/sclang -v` and found version 3.9.2
- found 3.9.2 with grep in /nix/store/a6z8q6az7fzhh0sp4llp4fzp8c95bm6y-supercollider-3.9.2
- directory tree listing: https://gist.github.com/5b90384fd1df273cba0757c752a352d6
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/umockdev/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/7lpv5i13wb3w9yzid1x1hymb4cwrjisa-umockdev-0.11.2/bin/umockdev-run -h` got 0 exit code
- ran `/nix/store/7lpv5i13wb3w9yzid1x1hymb4cwrjisa-umockdev-0.11.2/bin/umockdev-run --help` got 0 exit code
- ran `/nix/store/7lpv5i13wb3w9yzid1x1hymb4cwrjisa-umockdev-0.11.2/bin/umockdev-record -h` got 0 exit code
- ran `/nix/store/7lpv5i13wb3w9yzid1x1hymb4cwrjisa-umockdev-0.11.2/bin/umockdev-record --help` got 0 exit code
- found 0.11.2 with grep in /nix/store/7lpv5i13wb3w9yzid1x1hymb4cwrjisa-umockdev-0.11.2
- directory tree listing: https://gist.github.com/f15b0f7c88a9a3c931d00fe888311f2f
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/xpra/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra -h` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra --help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra --version` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra -h` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra --help` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/udev_product_version -h` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/udev_product_version --help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/udev_product_version help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra_launcher-wrapped -h` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra_launcher-wrapped --help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra_launcher-wrapped --version` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra_launcher-wrapped -h` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra_launcher-wrapped --help` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra_launcher -h` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra_launcher --help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra_launcher --version` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra_launcher -h` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/xpra_launcher --help` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/..xpra-wrapped-wrapped -h` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/..xpra-wrapped-wrapped --help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/..xpra-wrapped-wrapped --version` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/..xpra-wrapped-wrapped -h` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/..xpra-wrapped-wrapped --help` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra-wrapped -h` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra-wrapped --help` got 0 exit code
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra-wrapped --version` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra-wrapped -h` and found version 2.2.5
- ran `/nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5/bin/.xpra-wrapped --help` and found version 2.2.5
- found 2.2.5 with grep in /nix/store/fdgkwl5jg6lzkkf3s06xnljssfcwgpbg-xpra-2.2.5
- directory tree listing: https://gist.github.com/b8906f2abe5109a6ace5790246e4d62a
OpenSMTPD does not require the setuid bit for its `sendmail`. This works
around it by wrapping the called `sendmail` so that the wrapper falls
back on either the setuid `sendmail` or the non-setuid `sendmail`
depending on what's available.
The solution of relying on `$PATH` to be set is unfortunately
unreliable, as `mdadm --monitor` will likely be executed from a
`systemd` unit, that runs with a clean `$PATH`.
