All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-lxml: allow build as host package
Date: Tue, 24 Jan 2017 11:34:51 +1300	[thread overview]
Message-ID: <20170124113451.2af0d791@free-electrons.com> (raw)
In-Reply-To: <1485179476-6049-1-git-send-email-casantos@datacom.ind.br>

Hello,

On Mon, 23 Jan 2017 11:51:16 -0200, Carlos Santos wrote:
> 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.
> 
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>

I remain a little bit uncomfortable with host packages that have no
in-tree user, as it means the code is dead and never tested by our
autobuilder infrastructure.

That being said, lots of aspects of Buildroot are already not tested by
our autobuilder infra, so maybe my argument is not so good after all.

Peter, what is your feeling on this ?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-01-23 22:34 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 [this message]
2017-02-01 17:51 ` [Buildroot] [PATCH v2] " Carlos Santos
2017-02-14 11:20   ` Carlos Santos
2017-02-16 22:08     ` Arnout Vandecappelle
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=20170124113451.2af0d791@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 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.