unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Tanguy Le Carrour" <tanguy@bioneland.org>
Cc: 42390-done@debbugs.gnu.org
Subject: [bug#42390] [PATCH] gnu: Add python-mamba.
Date: Thu, 23 Jul 2020 21:19:39 +0200	[thread overview]
Message-ID: <f0d7f2a6-3030-323e-e771-7c1834b19faf@crazy-compilers.com> (raw)
In-Reply-To: <87v9ifj0mq.fsf@gnu.org>

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.

IMHO lint is a helper and coverage is used at build-time only most of
the time. This is why I added it to the list. YMMV, though.

In the case of python-mamba - which is a test-runner -,
"propagated-input" seems to be correct, so lint gives inaccurate advice
here.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |





  reply	other threads:[~2020-07-23 19:20 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 [this message]
2020-07-24  6:36         ` Tanguy Le Carrour
2020-07-24 13:14         ` Ludovic Courtès
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=f0d7f2a6-3030-323e-e771-7c1834b19faf@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=42390-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --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).