From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python-pillow: fix wrong install step
Date: Wed, 6 Jul 2016 15:15:07 +0200 [thread overview]
Message-ID: <20160706151507.11769b9c@free-electrons.com> (raw)
In-Reply-To: <CA+TH9V=cyeKKhvVtrjM0EowOUVrPqZjE8zADizy8F3Nr0__Eig@mail.gmail.com>
Hello,
On Wed, 6 Jul 2016 15:09:26 +0200, Angelo Compagnucci wrote:
> > Ah, ok. Thanks for the explanation. I hate to say I dislike what the
> > python-pillow package needs to do, but there isn't a better option for
> > now with the current python-package infrastructure. We'll live with
> > that for now, and potentially improve the python-package infrastructure
> > in the future if more packages have similar requirements.
>
> Well, yes, I proposed a solution on a thread months ago, but for now
> we a have such a requirement only for this package, so I convey with
> you that the problem not arises.
Agreed.
It is not clear to me if it is legal for a Python package to build only
with "build_ext" and not "build". According to the Python documentation
"build" should do everything, and "build_ext" is a sub-command to build
just the "extensions".
Maybe the problem should be reported upstream?
> > Ditto for the install target commands.
>
> Will do!
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-06 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 22:02 [Buildroot] [PATCH] package/python-pillow: fix wrong install step Angelo Compagnucci
2016-07-06 12:46 ` Thomas Petazzoni
2016-07-06 12:51 ` Angelo Compagnucci
2016-07-06 13:05 ` Thomas Petazzoni
2016-07-06 13:09 ` Angelo Compagnucci
2016-07-06 13:15 ` Thomas Petazzoni [this message]
2016-07-06 13:17 ` Angelo Compagnucci
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=20160706151507.11769b9c@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox