All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] python-cffi: always install target python-pycparser
Date: Sat, 16 Dec 2017 16:37:07 +0100	[thread overview]
Message-ID: <20171216163707.13cb65db@windsurf> (raw)
In-Reply-To: <20171213090424.11172-2-yegorslists@googlemail.com>

Hello,

On Wed, 13 Dec 2017 10:04:22 +0100, yegorslists at googlemail.com wrote:

> Some packages like python-crossbar, python-keyring use scripts,
> that check dependencies of all involved packages at runtime. And
> though cffi needs pycparser only in host variant during the bindings
> compilation, it still has pycparser in its setup.py as dependency.

It is not entirely clear to me what is happening here. Could you expand
a bit on this?

> So always installing pycparser along with cffi would create rather
> little overhead, but we won't have to check whether particular
> package has such a runtime script, that checks for dependencies.

I understand what you mean, but I find the wording confusing. It feels
as if you're saying that you're not going to do the change... that
you're doing in this commit.

What about:

"Since adding pycparser as a dependency to python-cffi adds only very
little overhead, we chose this solution as it avoids having to ..."

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-12-16 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  9:04 [Buildroot] [PATCH 1/4] python-more-itertools: new package yegorslists at googlemail.com
2017-12-13  9:04 ` [Buildroot] [PATCH 2/4] python-cffi: always install target python-pycparser yegorslists at googlemail.com
2017-12-16 15:37   ` Thomas Petazzoni [this message]
2017-12-16 21:14     ` Yegor Yefremov
2017-12-13  9:04 ` [Buildroot] [PATCH 3/4] python-secretstorage: new package yegorslists at googlemail.com
2017-12-16 15:35   ` Thomas Petazzoni
2017-12-13  9:04 ` [Buildroot] [PATCH 4/4] python-keyring: bump to version 10.5.0 yegorslists at googlemail.com
2017-12-13  9:05   ` Yegor Yefremov
2017-12-16 15:33 ` [Buildroot] [PATCH 1/4] python-more-itertools: new package Thomas Petazzoni

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=20171216163707.13cb65db@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 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.