unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: python-flask: Make python-click a propagated-input.
Date: Sun, 04 Dec 2016 19:07:51 +0100	[thread overview]
Message-ID: <87a8cbbma0.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161204111030.23002-1-dannym@scratchpost.org>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2016-12-04 18:07 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 [this message]
2016-12-07  5:57   ` Chris Marusich

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=87a8cbbma0.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@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.
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).