From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: "Nicolas Graves via Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org>,
lars@6xq.net, tanguy@bioneland.org, marius@gnu.org,
me@bonfacemunyoki.com, sharlatanus@gmail.com
Subject: Re: Python's native-inputs
Date: Mon, 22 Apr 2024 13:25:09 -0400 [thread overview]
Message-ID: <87wmopgvii.fsf@gmail.com> (raw)
In-Reply-To: <87o7a18ooz.fsf@ngraves.fr> (Nicolas Graves's message of "Mon, 22 Apr 2024 16:19:40 +0200")
Hi Nicolas,
Nicolas Graves <ngraves@ngraves.fr> writes:
[...]
> TL;DR :
> - patch series in big progress, not done yet because I don't really
> know where to stop and massive rebuilds.
> - WDYT about tweaking the build-system for pytest?
> - not done : tweaking the pypi import to ignore those packages. I've
> done it in the juliahub import code, but I haven't delved into that
> though.
> - not done : adding those packages to guix lint - trivial. We should
> probably add a variable in pypi import that is exported and added into
> guix lint.
>
> Acting on the three (guix import, guix lint, guix build) can make it
> quite easy on maintainers in the end IMO.
You're bringing good arguments. If you can pull it off in the way
outlined above, I agree it's be valuable to have.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-04-22 17:25 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.
2024-04-22 17:25 ` Maxim Cournoyer [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
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=87wmopgvii.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=ngraves@ngraves.fr \
--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 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).