unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: rekado <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add 'waf-build-system'.
Date: Wed, 04 Feb 2015 23:04:42 +0100	[thread overview]
Message-ID: <87a90tqqo5.fsf@gnu.org> (raw)
In-Reply-To: <87pp9qsjey.fsf@mango.localdomain> (rekado@elephly.net's message of "Tue, 03 Feb 2015 23:46:13 +0100")

rekado <rekado@elephly.net> skribis:

> Ludovic Courtès writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> Unlike the Python build system, however, there is a configure phase, and
>>> not everything important happens during the install phase.
>>
>> OK.  Did you find it more appropriate to extend ‘gnu-build-system’
>> rather than ‘python-build-system’?
>
> The way I see it the waf-build-system is a descendant of the
> gnu-build-system in that it has the same phases; it only uses a
> different tool (namely the waf script).  The python-build-system on the
> other hand concentrates everything in the install "phase".
>
> The waf-build-system looks similar to the python-build-system only
> because the waf script needs to be run with a python interpreter, and it
> could be either version 2 or 3.  This is why I extended the
> gnu-build-system (as a "parent") and imported the default-python
> procedures from python-build-system (as a "cousin").
>
> Does this make any sense?

Yes it does.  Thanks for the explanation!

Ludo’.

  reply	other threads:[~2015-02-04 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 21:48 [PATCH] Add 'waf-build-system' Ricardo Wurmus
2015-02-01 21:08 ` Ludovic Courtès
2015-02-03 22:46   ` rekado
2015-02-04 22:04     ` Ludovic Courtès [this message]
2015-02-05 21:53     ` Ricardo Wurmus
2015-02-07 23:26       ` Ludovic Courtès

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=87a90tqqo5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).