From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host
Date: Fri, 4 Jan 2019 09:58:11 +0100 [thread overview]
Message-ID: <20190104095811.33a189e4@windsurf> (raw)
In-Reply-To: <1870289102.225265.1546558443354.JavaMail.zimbra@datacom.com.br>
Hello Carlos,
On Thu, 3 Jan 2019 21:34:03 -0200 (BRST), Carlos Santos wrote:
> Well, I'm happy that my work helped you guys to analyze the pros and
> cons of having Config.in.host for all host packages. Looks like it's
> not a good idea, so I will mark the patches as refused in patchwork.
I don't think we can conclude yet "it's not a good idea". At this
point, my feeling is more: the consequences are worse than I initially
expected, which requires some more thoughts on how we want to handle
that.
Again, what was your motivation for adding those Config.in.host options
in the first place, specifically for waf ? Was it just about getting
this whole discussion started, and use waf just as a simple first
example ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-04 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 17:19 [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host Carlos Santos
2018-12-23 17:19 ` [Buildroot] [PATCH v3 2/3] doc/manual: document the waf packages may need to select host-waf Carlos Santos
2018-12-26 21:31 ` Thomas Petazzoni
2018-12-23 17:19 ` [Buildroot] [PATCH v3 3/3] package/mpv: selec host-waf Carlos Santos
2018-12-26 21:30 ` [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host Thomas Petazzoni
2018-12-26 21:55 ` Yann E. MORIN
2019-01-03 21:50 ` Thomas Petazzoni
2019-01-03 22:06 ` Yann E. MORIN
2019-01-03 22:14 ` Yann E. MORIN
2019-01-03 23:34 ` Carlos Santos
2019-01-04 8:58 ` Thomas Petazzoni [this message]
2019-01-04 10:05 ` Carlos Santos
2019-01-04 10:10 ` Thomas Petazzoni
2019-01-04 11:06 ` Arnout Vandecappelle
2019-01-04 11:51 ` Yann E. MORIN
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=20190104095811.33a189e4@windsurf \
--to=thomas.petazzoni@bootlin.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