From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 42390-done@debbugs.gnu.org, Tanguy Le Carrour <tanguy@bioneland.org>
Subject: [bug#42390] [PATCH] gnu: Add python-mamba.
Date: Fri, 24 Jul 2020 15:14:57 +0200 [thread overview]
Message-ID: <87y2n98372.fsf@gnu.org> (raw)
In-Reply-To: <f0d7f2a6-3030-323e-e771-7c1834b19faf@crazy-compilers.com> (Hartmut Goebel's message of "Thu, 23 Jul 2020 21:19:39 +0200")
Hi,
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 22.07.20 um 12:38 schrieb Ludovic Courtès:
>> Hartmut, it looks like there are cases like this where python-coverage
>> is used as a library and thus should not be in ‘native-inputs’. Should
>> we remove it from the list?
>
> This depends on whether you see "guix lint" as a helper or an enforcer -
> and on how one classifies this package.
The message is “python-coverage should probably be a native input”.
That suggests it’s unlikely (but not impossible) to be a false positive.
To me, we should keep python-coverage in the list only if we know it
should be a native input 90% of the time.
Tanguy, Hartmut, do you have an estimate here? :-)
Adding a package property to instruct ‘guix lint’ to ignore the issue
would also work, as Tanguy proposed.
Ludo’.
next prev parent reply other threads:[~2020-07-24 13:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 12:25 [bug#42390] [PATCH] gnu: Add python-mamba Tanguy Le Carrour
2020-07-21 16:41 ` bug#42390: " Ludovic Courtès
2020-07-22 7:36 ` [bug#42390] " Tanguy Le Carrour
2020-07-22 10:38 ` Ludovic Courtès
2020-07-23 19:19 ` Hartmut Goebel
2020-07-24 6:36 ` Tanguy Le Carrour
2020-07-24 13:14 ` Ludovic Courtès [this message]
2020-07-27 7:47 ` Hartmut Goebel
2020-07-27 8:10 ` Tanguy Le Carrour
2020-07-28 21:56 ` Ludovic Courtès
2020-07-29 6:52 ` Tanguy Le Carrour
2020-07-31 6:42 ` Tanguy Le Carrour
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=87y2n98372.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42390-done@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.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).