all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Alexis Simon <alexis.simon@runbox.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Python package with some rust dependency
Date: Sun, 18 Feb 2024 14:03:34 +1100	[thread overview]
Message-ID: <87frxqxym1.fsf@zancanaro.id.au> (raw)
In-Reply-To: <badd97d2-8b48-471b-b80d-80f32cadb13b@runbox.com> (Alexis Simon's message of "Sat, 17 Feb 2024 08:46:30 -0800")

On Sat, Feb 17 2024, Alexis Simon wrote:
> On 17/02/2024 03:50, Carlo Zancanaro wrote:
>> Also, as an aside, I'm not sure where the 'prepare-python-module
>> phase is coming from. Does it actually exist?
>
> This is a very good question I had myself and to which I couldn't find
> the answer. I found examples such as those [1] in the repo and
> couldn't find where this phase was specified. But it seems to work.

I don't doubt that this works at the moment, but I expect that
ed1b2d0a86a0a62d8d843f06669a5f072482c37e on core-updates will break this
(and any other packages that reference non-existent phases).

Packages in the guix repository will presumably be fixed during the
core-updates merge, but any other packages will need to be updated.

Carlo


      parent reply	other threads:[~2024-02-18  3:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  1:49 Python package with some rust dependency Alexis Simon
2024-02-12 23:29 ` Carlo Zancanaro
2024-02-13 19:36   ` Alexis Simon
2024-02-13 21:46     ` Carlo Zancanaro
2024-02-13 21:55       ` Alexis Simon
2024-02-16  6:08         ` Alexis Simon
2024-02-17  0:02           ` Alexis Simon
2024-02-17 11:50             ` Carlo Zancanaro
2024-02-17 16:46               ` Alexis Simon
2024-02-17 19:25                 ` Alexis Simon
2024-02-18  3:03                 ` Carlo Zancanaro [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87frxqxym1.fsf@zancanaro.id.au \
    --to=carlo@zancanaro.id.au \
    --cc=alexis.simon@runbox.com \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.