with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
I removed the "propagatedbuildInputs" line because it's misspelled, and
so will never have worked. Nobody seems to have complained, so
presumably wasn't necessary.
Semi-automatic update. These checks were done:
- built on NixOS
- ran `/nix/store/x1h0gya1nb2kxbvkcr8sivskx2kzycdr-pipelight-0.2.8.2/bin/pipelight-plugin --help` got 0 exit code
- ran `/nix/store/x1h0gya1nb2kxbvkcr8sivskx2kzycdr-pipelight-0.2.8.2/bin/pipelight-plugin --version` and found version 0.2.8.2
- found 0.2.8.2 with grep in /nix/store/x1h0gya1nb2kxbvkcr8sivskx2kzycdr-pipelight-0.2.8.2
- found 0.2.8.2 in filename of file in /nix/store/x1h0gya1nb2kxbvkcr8sivskx2kzycdr-pipelight-0.2.8.2
This release in a RC for gnupg-2.2. The main difference as far as
nixpkgs is concerned is that the binary `gpg2` is now called `gpg` and
`gpgv2` is called `gpgv`.
This update fixed all explicit use of `gpg2` and `gpgv2` across nixpkgs,
but there might be some packaged software that internally use `gpg2`
not handeled by this commit.
See http://lists.gnu.org/archive/html/info-gnu/2017-08/msg00001.html
for full release information
* pkgs: refactor needless quoting of homepage meta attribute
A lot of packages are needlessly quoting the homepage meta attribute
(about 1400, 22%), this commit refactors all of those instances.
* pkgs: Fixing some links that were wrongfully unquoted in the previous
commit
* Fixed some instances
This seems to have been confusing people, using both xlibs and xorg, etc.
- Avoided renaming local (and different) xlibs binding in gcc*.
- Fixed cases where both xorg and xlibs were used.
Hopefully everything still works as before.
This reverts commit cd52c04456 and
others.
Managing certificates (including revoking certificates and adding
custom certificates) becomes extremely painful if every package in the
system potentially depends on a different copy of cacert. Also, it
makes updating cacert rather expensive.
