diff options
| author | Ludovic Courtès <ludo@gnu.org> | 2019-09-06 14:41:58 +0200 |
|---|---|---|
| committer | Ludovic Courtès <ludo@gnu.org> | 2019-09-06 14:41:58 +0200 |
| commit | bc60349b5bc58a0b803df5adce1de6db82453744 (patch) | |
| tree | d11777318a93c1f85b579f9e86c7bd402e52b368 /po | |
| parent | d2d63e20d5b981009b61bf416b4d7b516e8f1f34 (diff) | |
| download | guix-bc60349b5bc58a0b803df5adce1de6db82453744.tar.gz | |
packages: 'supported-package?' binds '%current-system' for graph traversal.
Previously, (supported-package? coreutils "armhf-linux")
with (%current-system) = "x86_64-linux" would return false. That's
because 'supported-package?' would traverse the x86_64 dependency graph,
which contains 'tcc-boot0', which supports x86 only.
Consequently, 'supported-package?' would match only 53 packages for
"armhf-linux" when running on x86, as is the case during continuous
integration.
* guix/packages.scm (package-transitive-supported-systems): Add an
optional 'system' parameter. Use 'mlambda' instead of 'mlambdaq' for
memoization.
(supported-package?): Pass 'system' to 'package-transitive-supported-systems'.
* tests/packages.scm ("package-transitive-supported-systems, implicit inputs")
("package-transitive-supported-systems: reduced binary seed, implicit inputs"):
Remove calls to 'invalidate-memoization!', which no longer work and were
presumably introduced to work around the bug we're fixing (see commit
0db65c168fd6dec57a357735fe130c80feba5460).
* tests/packages.scm ("supported-package?"): Rewrite test to use only
existing system name since otherwise 'bootstrap-executable' raises an
exception.
("supported-package? vs. system-dependent graph"): New test.
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions