From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 39447-close@debbugs.gnu.org, Amin Bandali <mab@gnu.org>
Subject: bug#39447: [PATCH] gnu: Add python-gandi.cli.
Date: Fri, 14 Feb 2020 00:25:55 +0100 [thread overview]
Message-ID: <87d0ai5at8.fsf@nckx> (raw)
In-Reply-To: <20200206031305.20513-1-mab@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Amin,
Amin Bandali 写道:
> * gnu/packages/python-xyz.scm (python-gandi.cli): New variable.
Thanks! This package is already in Guix as ‘gandi.cli’ — we avoid
the ‘python-’ prefix for stand-alone programmes since being
written in Python (or any other language) is irrelevant.
+ (propagated-inputs
+ `(("git" ,git)
+ ("openssh" ,openssh)
+ ("openssl" ,openssl)
+ ("python-click" ,python-click)
+ ("python-ipy" ,python-ipy)
+ ("python-pyyaml" ,python-pyyaml)
+ ("python-requests" ,python-requests)
+ ("python-setuptools" ,python-setuptools)))
Propagation should be avoided when possible, although it's (sadly)
more common in Python packages than elsewhere.
However, propagating inputs like git, openssh, openssl,
python-setuptools… is definitely wrong. Was this deliberate?
Which problem were you trying to solve? Take a look at
gandi.cli's ‘embed-store-file-names’ for a different approach that
avoids propagation altogether.
I'm closing this bug, but please let me know if the existing
gandi.cli is missing features. I added it but haven't used it in
a while.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-02-13 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 3:13 [bug#39447] [PATCH] gnu: Add python-gandi.cli Amin Bandali
2020-02-13 22:25 ` Ludovic Courtès
2020-02-13 23:25 ` Tobias Geerinckx-Rice via Guix-patches via [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=87d0ai5at8.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=39447-close@debbugs.gnu.org \
--cc=mab@gnu.org \
--cc=me@tobias.gr \
/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).