From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/python3-setuptools: new package
Date: Sun, 30 Dec 2018 14:24:07 +0100 [thread overview]
Message-ID: <20181230142407.69d10ba8@windsurf> (raw)
In-Reply-To: <CADvTj4qinyrbrutcb_WkO4rveJgA9i9F6bX9Txhp+MAWxZSyfg@mail.gmail.com>
Hello,
On Sun, 30 Dec 2018 06:10:04 -0600, James Hilliard wrote:
> > Could you instead test if those patches also work for you ?
> Looks good, I was able to successfully do a clean build with my meson
> version bump patch on top.
Thanks for the confirmation. Do you know what changed in Meson that
makes it *require* setuptools? As I explained in the cover letter of my
Python 3 Setuptools series, meson (at least in the version we currently
have in Buildroot) uses setuptools if available, and otherwise falls
back to distutils, which is why it has been working well so far without
a python3-setuptools package.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-30 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 6:41 [Buildroot] [PATCH 1/2] package/python3-setuptools: new package james.hilliard1 at gmail.com
2018-12-30 6:41 ` [Buildroot] [PATCH 2/2] package/meson: bump to version 0.49.0 james.hilliard1 at gmail.com
2019-01-01 10:30 ` Thomas Petazzoni
2018-12-30 11:19 ` [Buildroot] [PATCH 1/2] package/python3-setuptools: new package Thomas Petazzoni
2018-12-30 12:10 ` James Hilliard
2018-12-30 13:24 ` Thomas Petazzoni [this message]
2018-12-30 18:15 ` Asaf Kahlon
2018-12-31 14:35 ` 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=20181230142407.69d10ba8@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