all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 2/4] gnu: Add xcffib
Date: Wed, 17 Dec 2014 10:01:43 +0100	[thread overview]
Message-ID: <878ui6myyw.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPP6UOwbkT1vm_tW99Cn_KcyOTb4_yKP4wNV7V6fQtDj0w@mail.gmail.com> (Federico Beffa's message of "Tue, 16 Dec 2014 18:17:38 +0100")

Federico Beffa <beffa@ieee.org> skribis:

> On Mon, Dec 15, 2014 at 11:16 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> +    (propagated-inputs
>>> +     `(("python-cffi" ,python-cffi)))
>>
>> Please add a comment saying why this is propagated.
>
> The reason is that I want the package to inherit the propagated inputs
> from 'python-cffi' as the latter requires 'python-pycparser' at run
> time. If I don't make python-cffi a propagated-input, but a normal
> input, I need to copy the propagated-inputs from that package and
> (re-) make them propagated-inputs of python-xcffib as well.

Oh, I see.  But that’s basically because xcffib does “import cffi” or
something like that, right?

In that case I would just add a comment saying that, unless you really
think it’s obvious (it wasn’t to me, initially.)

> A similar reason applier to python-xcffib in python-cairocffi and to
> pygobject + python-cairocffi + gobject-introspection + pathon-pycairo
> in python-matplotlib.
>
> Is that OK?

Yes.  Thanks for explaining!

Ludo’.

  reply	other threads:[~2014-12-17  9:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14 19:40 [PATCH 2/4] gnu: Add xcffib Federico Beffa
2014-12-15 22:16 ` Ludovic Courtès
2014-12-16 17:17   ` Federico Beffa
2014-12-17  9:01     ` Ludovic Courtès [this message]
2014-12-17 16:57   ` Federico Beffa
2014-12-17 20:28     ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878ui6myyw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.