From: "Wiktor Żelazny" <wz@freeshell.de>
To: help-guix@gnu.org
Subject: Re: how to define inputs for python packages
Date: Mon, 28 Sep 2020 10:28:57 +0200 [thread overview]
Message-ID: <20200928082857.uuolj4he4tad3a45@wzguix> (raw)
In-Reply-To: <20200928093559.5b7d4bde@panther-arch.localdomain>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Mon, Sep 28, 2020 at 09:35:59AM +0330, Reza Alizadeh Majd wrote:
> is there any rule that I missed to choose a dependency as an `input` or
> as a `propageted-input` one?
Hi,
I’d say that you always need to declare `python-*` dependencies as
`propagated-inputs`, unless it’s something required for building and
testing the package, exclusively, in which case the package in question
goes to `native-inputs`.
As an aside, it’s the same for `r-*` packages.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2020-09-28 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 6:05 how to define inputs for python packages Reza Alizadeh Majd
2020-09-28 8:28 ` Wiktor Żelazny [this message]
2020-09-28 18:27 ` Hartmut Goebel
2020-09-29 9:02 ` Reza Alizadeh Majd
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=20200928082857.uuolj4he4tad3a45@wzguix \
--to=wz@freeshell.de \
--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.
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).