From: Chris Marusich <cmmarusich@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: python-flask: Make python-click a propagated-input.
Date: Tue, 06 Dec 2016 21:57:47 -0800 [thread overview]
Message-ID: <87oa0oth5w.fsf@gmail.com> (raw)
In-Reply-To: <87a8cbbma0.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Sun, 04 Dec 2016 19:07:51 +0100")
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Marius Bakke <mbakke@fastmail.com> writes:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> * gnu/packages/python.scm (python-click)[native-inputs]: Move to ...
>> [propagated-inputs]: ... here.
>> ---
>> gnu/packages/python.scm | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
>> index 8f8b0de72..9c3902c3e 100644
>> --- a/gnu/packages/python.scm
>> +++ b/gnu/packages/python.scm
>> @@ -9153,9 +9153,8 @@ useful for solving the Assignment Problem.")
>> (propagated-inputs
>> `(("python-itsdangerous" ,python-itsdangerous)
>> ("python-jinja2" ,python-jinja2)
>> - ("python-werkzeug" ,python-werkzeug)))
>> - (native-inputs
>> - `(("python-click" ,python-click)))
>> + ("python-werkzeug" ,python-werkzeug)
>> + ("python-click" ,python-click)))
>
> The commit message and diff is contradictory :) Did you mean to make
> python-werkzeug a native-input?
>
The diff here looks correct; Danny removed the native-input line, so the
result is that python-werkzeug and python-click are both
propagated-inputs.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-12-07 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 11:10 [PATCH] gnu: python-flask: Make python-click a propagated-input Danny Milosavljevic
2016-12-04 18:07 ` Marius Bakke
2016-12-07 5:57 ` Chris Marusich [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=87oa0oth5w.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).