From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] python-lxml: allow build as host package
Date: Thu, 16 Feb 2017 23:08:17 +0100 [thread overview]
Message-ID: <8c9bf0e5-d389-e61c-efc8-8e75da9bc423@mind.be> (raw)
In-Reply-To: <373030528.10239603.1487071200627.JavaMail.zimbra@datacom.ind.br>
On 14-02-17 12:20, Carlos Santos wrote:
>> From: "Carlos Santos" <casantos@datacom.ind.br>
>> To: buildroot at buildroot.org
>> Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
>> Sent: Wednesday, February 1, 2017 3:51:08 PM
>> Subject: [Buildroot] [PATCH v2] python-lxml: allow build as host package
>
>> While currently there is no in-tree Buildroot package which depends on
>> host-python-lxml, we (DATACOM) have some proprietary modules that use it
>> in their test scripts.
>>
>> We tested python-lxml as host package and confirmed that it builds and
>> works correctly. Someone else might require it, so we are proposing its
>> inclusion.
>
> Hello,
>
> Any news about this proposal? I think it could fall into the new policy of
> "loosen up a little on accepting host tools"[1] if I add the corresponding
> Config.in.host, right? I know I'm pushing here, but host-python-lxml would
> help us (DATACOM) to have more reproducible builds.
>
> 1. http://elinux.org/Buildroot:DeveloperDaysFOSDEM2017#Host_packages_with_no_in-tree_user
We didn't reach a satisfactory conclusion for this case. We (or at least I :-)
certainly understand your need. But it is really weird to see a completely
random python package appear in the host tools menu. I personally don't mind
that much, but if all 265 host packages would appear in the menu it would get a
little bit overloaded...
*Some* way to include it in the autobuilders is certainly needed. As written in
the report: "Maybe for these it's not even so important that they are tested in
the autobuilder - almost nobody is going to use it anyway. However, in that case
it's not very useful to have it anyway. Especially because it almost certainly
will break at some point. "
So, no clear answer I'm afraid...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-02-16 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 13:51 [Buildroot] [PATCH] python-lxml: allow build as host package Carlos Santos
2017-01-23 22:34 ` Thomas Petazzoni
2017-02-01 17:51 ` [Buildroot] [PATCH v2] " Carlos Santos
2017-02-14 11:20 ` Carlos Santos
2017-02-16 22:08 ` Arnout Vandecappelle [this message]
2017-02-27 11:43 ` Carlos Santos
2017-04-01 16:45 ` 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=8c9bf0e5-d389-e61c-efc8-8e75da9bc423@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.