From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libsoup: needs host-python3
Date: Thu, 30 Aug 2018 21:11:25 +0300 [thread overview]
Message-ID: <87va7rwwqa.fsf@tkos.co.il> (raw)
In-Reply-To: <20180830171024.6d200527@windsurf>
Hi Asaf, Thomas,
Thomas Petazzoni writes:
> On Thu, 30 Aug 2018 13:14:30 +0300, Asaf Kahlon wrote:
>> The tld-parser script in libsoup is now written in Python,
>> and needs python3 to run.
>>
>> Fixes:
>> http://autobuild.buildroot.net/results/91c2d6a1ca011787130db06695d6cd9e882f7258
>> http://autobuild.buildroot.net/results/a318e595f02937534b3f8698ef4c04194a8b34af
>>
>> Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
>>
>> ---
>>
>> Maybe this specific script can run even with python2, but I don't think patchting the
>> "/usr/bin/env python3" line would be the right solution, especially considering
>> the fact that they already have python3-only code in recent commits.
Which commits do you refer to? The get_apache_module_dirs.py script is
only used by the meson build system, as far as I can see.
> Meh, I was hoping we could avoid the host-python3 dependency :-/
Later commits remove this script entirely. So we might be able to remove
this dependency in the future.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-08-30 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 10:14 [Buildroot] [PATCH 1/1] package/libsoup: needs host-python3 Asaf Kahlon
2018-08-30 15:10 ` Thomas Petazzoni
2018-08-30 18:11 ` Baruch Siach [this message]
2018-08-30 18:51 ` Asaf Kahlon
2018-09-01 13:53 ` 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=87va7rwwqa.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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