From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 0/3] dbus-python cleanup and python3 support
Date: Sat, 22 Nov 2014 19:37:45 +0100 [thread overview]
Message-ID: <878uj3ulmu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20141122192456.69ad67bd@free-electrons.com> (Thomas Petazzoni's message of "Sat, 22 Nov 2014 19:24:56 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> Dear Peter Korsgaard,
> On Thu, 20 Nov 2014 14:53:28 +0100, Peter Korsgaard wrote:
>> Peter Korsgaard (3):
>> dbus-python: cleanup package
>> python3: add patch to fix --includes / --ldflags output of python3-config
>> dbus-python: add python3 support
> Thanks, series applied to next. Probably the first time that I apply
> some patches from you :-)
;)
> I found one minor issue: on the last patch, you forgot to update the
> dependencies of the comment, so I added the following change to your
> patch:
> comment "dbus-python needs a toolchain w/ wchar, threads"
> - depends on BR2_PACKAGE_DBUS && BR2_PACKAGE_PYTHON
> + depends on BR2_PACKAGE_DBUS && (BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3)
Ahh yes, thanks
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-11-22 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 13:53 [Buildroot] [PATCH next 0/3] dbus-python cleanup and python3 support Peter Korsgaard
2014-11-20 13:53 ` [Buildroot] [PATCH next 1/3] dbus-python: cleanup package Peter Korsgaard
2014-11-20 13:53 ` [Buildroot] [PATCH next 2/3] python3: add patch to fix --includes / --ldflags output of python3-config Peter Korsgaard
2014-11-20 13:53 ` [Buildroot] [PATCH next 3/3] dbus-python: add python3 support Peter Korsgaard
2014-11-22 18:24 ` [Buildroot] [PATCH next 0/3] dbus-python cleanup and " Thomas Petazzoni
2014-11-22 18:37 ` Peter Korsgaard [this message]
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=878uj3ulmu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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