From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-reentry: add host variant
Date: Tue, 22 Oct 2019 22:27:07 +0200 [thread overview]
Message-ID: <20191022222707.21f2d917@windsurf> (raw)
In-Reply-To: <CALFsTFXTicPF07+mTzSsM4apHCM_jEis66TEFV2ASoSo5+gk2g@mail.gmail.com>
On Mon, 21 Oct 2019 12:00:49 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:
> > Why do we need a host variant for python-reentry ?
>
> That's because packages which use reentry will probably have
"probably" ?
> setup_requires=['reentry'] and reentry_register=True in their
> setup.py.
> On installation, reentry creates a file with the registered
> entrypoints that you can read on the target when you need to load
> them.
> Maybe I should send a v2 and explain that in the commit?
Yes, we will need a better commit log, but more importantly, do we have
any package in Buildroot that needs this ? Or is it custom/private
packages that you have ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-22 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 19:01 [Buildroot] [PATCH 1/1] package/python-flask: bump version to 1.1.1 Asaf Kahlon
2019-10-20 19:01 ` [Buildroot] [PATCH 1/1] package/python-reentry: add host variant Asaf Kahlon
2019-10-21 8:05 ` Thomas Petazzoni
2019-10-21 9:00 ` Asaf Kahlon
2019-10-22 20:27 ` Thomas Petazzoni [this message]
2019-10-23 19:27 ` Asaf Kahlon
2019-10-21 18:47 ` [Buildroot] [PATCH 1/1] package/python-flask: bump version to 1.1.1 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=20191022222707.21f2d917@windsurf \
--to=thomas.petazzoni@bootlin.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