From: ludo@gnu.org (Ludovic Courtès)
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: The waf problem (running nondeterministic binary blobs at build)
Date: Sun, 01 May 2016 15:25:46 +0200 [thread overview]
Message-ID: <87eg9lap0l.fsf@gnu.org> (raw)
In-Reply-To: <1462060525.745798.594497289.456F27DF@webmail.messagingengine.com> (Alex Griffin's message of "Sat, 30 Apr 2016 18:55:25 -0500")
Alex Griffin <a@ajgrf.com> 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 parent reply other threads:[~2016-05-01 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 13:20 The waf problem (running nondeterministic binary blobs at build) rain1
2016-04-26 10:16 ` Ludovic Courtès
2016-04-30 23:55 ` Alex Griffin
2016-05-01 13:25 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg9lap0l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=a@ajgrf.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).