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 20:31:00 +0200	[thread overview]
Message-ID: <20130910183100.GA6819@debian> (raw)
In-Reply-To: <87txhsbma9.fsf@gnu.org>

On Tue, Sep 10, 2013 at 07:48:30PM +0200, Ludovic Courtès wrote:
> You’re mixing different things: the line above is on the host side,
> whereas the patch I proposed changes the modules imported on the build
> side.

Okay, I get it!

> Can you try this patch to check the value of ‘phases’?

Without your previous patch, I get the following:

;;; (the-python-phases ((set-paths . #<procedure set-paths (#:key target inputs native-inputs search-paths native-search-paths)>) (unpack . #<procedure unpack (#:key source)>) (patch . #<procedure patch (#:key patches patch-flags)>) (patch-source-shebangs . #<procedure patch-source-shebangs (#:key source)>) (configure . #<procedure configure (#:key target native-inputs inputs outputs configure-flags out-of-source?)>) (patch-generated-file-shebangs . #<procedure patch-generated-file-shebangs rest>) (build . #<procedure build (#:key make-flags parallel-build?)>) (check . #<procedure check (#:key target make-flags tests? test-target parallel-tests?)>) (install . #<procedure 1c90070 at ice-9/eval.scm:264:7 %args>) (patch-shebangs . #<procedure patch-shebangs (#:key outputs patch-shebangs?)>) (
 strip . #<procedure strip (#:key target outputs strip-binaries? strip-command objcopy-command strip-flags strip-directories)>)))
WARNING: (guile-user): `%standard-phases' imported from both (guix build python-build-system) and (guix build gnu-build-system)


After applying your previous patch, I get this:

;;; (the-python-phases ((set-paths . #<procedure set-paths (#:key target inputs native-inputs search-paths native-search-paths)>) (unpack . #<procedure unpack (#:key source)>) (patch . #<procedure patch (#:key patches patch-flags)>) (patch-source-shebangs . #<procedure patch-source-shebangs (#:key source)>) (patch-generated-file-shebangs . #<procedure patch-generated-file-shebangs rest>) (build . #<procedure build empty>) (check . #<procedure check (#:key tests? test-target)>) (install . #<procedure b92230 at ice-9/eval.scm:264:7 %args>) (wrap . #<procedure wrap (#:key inputs outputs)>) (patch-shebangs . #<procedure patch-shebangs (#:key outputs patch-shebangs?)>) (strip . #<procedure strip (#:key target outputs strip-binaries? strip-command objcopy-command strip-flags strip-directories)>)
 ))


So indeed, your patch solves the confusion!

Thanks, I will push it then.

Andreas

  reply	other threads:[~2013-09-10 18:31 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
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 [this message]
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=20130910183100.GA6819@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).