[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The waf problem (running nondeterministic binary blobs at build)
From: |
Ludovic Courtès |
Subject: |
Re: The waf problem (running nondeterministic binary blobs at build) |
Date: |
Sun, 01 May 2016 15:25:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Alex Griffin <address@hidden> skribis:
> Debian replaces all binary 'waf' files with their own
> 'waf-uncompressed'. I think our python-waf package should be altered to
> produce an uncompressed version, then the waf-build-system should
> automatically use that (look at the python-pycairo package for an
> example of using the system's waf version instead of the bundled one).
Sounds like a plan. We can take this route and adjust if we stumble
upon incompatibilities.
Apparently we’d have 20 packages to audit:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use(guix)
scheme@(guile-user)> ,use(gnu)
scheme@(guile-user)> ,use(guix build-system waf)
scheme@(guile-user)> (fold-packages (lambda (p n)
(if (eq? (package-build-system p)
waf-build-system)
(1+ n)
n))
0)
$2 = 20
--8<---------------cut here---------------end--------------->8---
We can do that incrementally, and patches going in that direction would
be welcome!
Thanks for your feedback,
Ludo’.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: The waf problem (running nondeterministic binary blobs at build),
Ludovic Courtès <=