With the 2.9 release the license got clarified to be hpnd.
* gnu/packages/xdisorg.scm (libwacom): Update to 2.11.0.
[native-inputs]: Remove python-evdev.
[inputs]: Add python, python-libevdev, python-pyudev.
[propagated-inputs]: Add libevdev.
[license]: Correct license to hpnd.
Change-Id: Ib5276beaec2c23e74532cb157225fc3a9a2e25e7
Signed-off-by: Christopher Baines <mail@cbaines.net>
Rather than creating a different builder in the store for every different
download (by hash), remove the hash from the builder and pass it in via an
environment variable. This means that when git-fetch is used by two different
package sources, the derivations will still differ but the builder will be
shared.
It used to be this way, but changed with
264fdbcaff. I noticed this through looking at
the same problem with svn-multi-fetch.
To try and make the effects of introducing variance in to the builder script
more obvious, separate it out in to it's own procedure, so that it's clearer
when there's new data going in that could cause variance.
* guix/git-download.scm (git-fetch/in-band*): Extract out builder script,
include hash in the derivation as an environment variable and update the
comment to be more directive.
(git-fetch-builder): New procedure.
Change-Id: I59c9fc445667c0e7dc44bcb706818300c394a1e5
Rather than creating a different builder in the store for every different
download (by hash), remove the hash from the builder and pass it in via an
environment variable. This means that when hg-fetch is used by two different
package sources, the derivations will still differ but the builder will be
shared.
Looking at the code, becuase the ref is also in the builder, the builders have
been duplicated for a while. The overhead is probably limited though since
hg-reference isn't used much compared to say svn-multi-reference.
To try and make the effects of introducing variance in to the builder script
more obvious, separate it out in to it's own procedure, so that it's clearer
when there's new data going in that could cause variance.
* guix/hg-download.scm (hg-fetch): Extract out builder script and include
hash, hg ref url, and hg ref changeset in the derivation as an environment
variables.
(hg-fetch-builder): New procedure.
Change-Id: I3c3a0b4963ea1b208bf1d5137ef98666458ae2d7
Rather than creating a different builder in the store for every different
download (by hash), remove the hash from the builder and pass it in via an
environment variable. This means that when svn-fetch is used by two different
package sources, the derivations will still differ but the builder will be
shared.
It used to be this way, but changed with
0e73f933b2. I noticed the hash in the builder
script when wondering why the build coordinator on bayfront was substituting
svn-multi-download files over and over again.
To try and make the effects of introducing variance in to the builder script
more obvious, separate it out in to it's own procedure, so that it's clearer
when there's new data going in that could cause variance.
* guix/svn-download.scm (svn-fetch): Extract out builder script, include hash
in the derivation as an environment variable and update the comment to be more
directive.
(svn-fetch-builder): New procedure.
Change-Id: I256b94666296ad747f494f0b497ca209b77fbfb4
Rather than creating a different builder in the store for every different
download (by hash), remove the hash from the builder and pass it in via an
environment variable. This means that when svn-multi-fetch is used by two
different package sources, the derivations will still differ but the builder
will be shared.
It used to be this way, but changed with
0e73f933b2. I noticed the hash in the builder
script when wondering why the build coordinator on bayfront was substituting
svn-multi-download files over and over again.
To try and make the effects of introducing variance in to the builder script
more obvious, separate it out in to it's own procedure, so that it's clearer
when there's new data going in that could cause variance.
* guix/svn-download.scm (svn-multi-fetch): Extract out builder script, include
hash in the derivation as an environment variable and update comment to be
more directive.
(svn-multi-fetch-builder): New procedure.
Change-Id: I83c60140ae09e189ee5e5428038a9428ecb8e281
* guix/transformations.scm (tuning-compiler): Adjust the wrapper script
when building for powerpc* architectures to pass the correct flags.
Change-Id: I9d809ac9b707eb8d6afa7b843c95bce29862a752
* gnu/packages/golang.scm (go-github-com-sergi-go-diff): Move from here ...
* gnu/packages/golang-xyz.scm: ... to here.
Change-Id: If722317a42006e3bef4462b5a6fe4c0f434bd5d2
* gnu/packages/golang-xyz.scm (go-gopkg-in-cheggaaa-pb-v1): Update to 1.0.29.
[arguments]: Set the import path to "github.com/cheggaaa/pb".
Change-Id: I0042b64c44386d588bad7779444f1f6652619a2d
Signed-off-by: Sharlatan Hellseher <sharlatanus@gmail.com>
* gnu/packages/tex.scm (texlive-latexindent)[arguments]<#:phases>: Wrap Perl
script so it can find Perl libraries.
[inputs]: Add PERL-FILE-HOMEDIR and PERL-YAML-TINY.
Signed-off-by: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Change-Id: I428c20f0c8aa49cc8273f41512f37b3622347ecc
This package was introduced in abfef465b2 as a
dependency for Nsncd. We can build Nsncd just fine, but building explicitly
this package is failing. The issue comes from two tests making assumption
about domain name resolution. The Guix build sandbox breaks these assumptions,
preventing the test suite to succeed. Fixing this by disabling the faulty
tests.
* gnu/packages/crates-io.scm (rust-dns-lookup-2): Skip faulty tests.
Change-Id: Idc42822d8cd72e83e9ea973820b5073ff87ad4d4
Signed-off-by: Christopher Baines <mail@cbaines.net>
To avoid duplicating go-github-com-alecthomas-kingpin.
* gnu/packages/golang-xyz.scm (go-gopkg-in-alecthomas-kingpin-v2)[name]: Set
to go-gopkg-in-alecthomas-kingpin-v2.
Change-Id: I1f9d2766c03393ac1268dafe490d25a7e57f7bc4
As it's redundant as of 1039ec03be.
* gnu/packages/python-xyz.scm (python-pyproject-metadata-0.7): Remove
variable.
* gnu/packages/build-tools.scm (meson-python): Use python-pyproject-metadata
rather than python-pyproject-metadata-0.7.
Change-Id: I50d458ff636cfab3a262e7d0759e88f14f68081f
