From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>,
"Nicolas Graves via Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
lars@6xq.net, tanguy@bioneland.org, marius@gnu.org,
me@bonfacemunyoki.com, sharlatanus@gmail.com
Subject: Re: Python's native-inputs
Date: Thu, 25 Apr 2024 18:03:39 +0200 [thread overview]
Message-ID: <87wmol5t0k.fsf@ngraves.fr> (raw)
In-Reply-To: <87frvd1mvl.fsf@elephly.net>
Hi Guix,
Just to let you know, I just added a working patch series that does this
job on (guix build, guix import pypi, guix lint). This is not the full
patch series, which I have rebased on python-team, but it should be good
enough
1) to test it
2) to review it for a v2 that would be more guixy
It's in 70570.
Cheers,
Nicolas
On 2024-04-22 16:40, Ricardo Wurmus wrote:
>> TL;DR :
>> - patch series in big progress, not done yet because I don't really
>> know where to stop and massive rebuilds.
>
> Please take a look at the python-team branch, which contains changes to
> the build system.
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2024-04-25 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 5:25 Python's native-inputs Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-04-19 2:07 ` Maxim Cournoyer
[not found] ` <draft-87pluisvqb.fsf@ngraves.fr>
2024-04-22 14:19 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-04-22 14:40 ` Ricardo Wurmus
2024-04-23 21:08 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2024-04-25 16:03 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution. [this message]
2024-04-22 17:25 ` Maxim Cournoyer
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=87wmol5t0k.fsf@ngraves.fr \
--to=guix-devel@gnu.org \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=me@bonfacemunyoki.com \
--cc=ngraves@ngraves.fr \
--cc=rekado@elephly.net \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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.