All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] python-lxml: allow build as host package
Date: Tue, 14 Feb 2017 09:20:00 -0200 (BRST)	[thread overview]
Message-ID: <373030528.10239603.1487071200627.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <1485971468-3709-1-git-send-email-casantos@datacom.ind.br>

> 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

Carlos Santos (Casantos) - DATACOM, P&D
?Something must be done. This is something. Therefore we must do it.?
(from the BBC series ?Yes, Prime Minister?, ?Power to the people?)

  reply	other threads:[~2017-02-14 11:20 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 [this message]
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=373030528.10239603.1487071200627.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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.