The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
There ver very many conflicts, basically all due to
name -> pname+version. Fortunately, almost everything was auto-resolved
by kdiff3, and for now I just fixed up a couple evaluation problems,
as verified by the tarball job. There might be some fallback to these
conflicts, but I believe it should be minimal.
Hydra nixpkgs: ?compare=1538299
Semi-automatic update. These checks were performed:
- built on NixOS
- ran `/nix/store/4x18w356x6ah895mfb17ascylzpp64py-kpcli-3.2/bin/kpcli -h` got 0 exit code
- ran `/nix/store/4x18w356x6ah895mfb17ascylzpp64py-kpcli-3.2/bin/kpcli --help` got 0 exit code
- found 3.2 with grep in /nix/store/4x18w356x6ah895mfb17ascylzpp64py-kpcli-3.2
- found 3.2 in filename of file in /nix/store/4x18w356x6ah895mfb17ascylzpp64py-kpcli-3.2
cc "@j-keck"
* 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