unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Python-build-system does not honour phases
Date: Tue, 10 Sep 2013 10:26:55 +0200	[thread overview]
Message-ID: <20130910082655.GA8621@debian> (raw)
In-Reply-To: <87hadtfzk4.fsf@gnu.org>

On Mon, Sep 09, 2013 at 11:35:55PM +0200, Ludovic Courtès wrote:
> The problem is that both the gnu-build-system and the
> python-build-system were getting imported, and both export a
> ‘%standard-phases’.

That is what I thought. I tried to add a
  #:use-module ((guix build-system gnu)
                #:select (gnu-build-system))
but that was not enough.

> The fix is to use only python-build-system:

That also does not seem to work. I split out the packages into two modules,
python for the python binaries that use gnu-build-system, and python-modules
for the packages using python-build-system.

The same error occurs, (alist-replace %standard-build-system) ends up with
the configure from gnu-build-system. 

Could it have something to do with the way %standard-phases of python are
derived from those of gnu? Or that code is quoted and executed in a different
environment from where it is written?

Maybe we should try to use a variable name %python-standard-phases instead.

Andreas

  reply	other threads:[~2013-09-10  8:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 22:26 Python-build-system does not honour phases Andreas Enge
2013-09-09 21:35 ` Ludovic Courtès
2013-09-10  8:26   ` Andreas Enge [this message]
2013-09-10 13:28     ` Andreas Enge
2013-09-10 17:53       ` Ludovic Courtès
2013-09-10 19:07         ` Andreas Enge
2013-09-10 19:27           ` Andreas Enge
2013-09-10 21:20             ` Ludovic Courtès
2013-09-10 21:34               ` Andreas Enge
2013-09-11 13:55                 ` Andreas Enge
2013-09-11 17:45                   ` Ludovic Courtès
2013-09-10 17:48     ` Ludovic Courtès
2013-09-10 18:31       ` Andreas Enge
2013-09-10 21:18         ` 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=20130910082655.GA8621@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).