[Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host

[Carlos Santos <casantos@datacom.com.br>]

> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "Carlos Santos" <casantos@datacom.com.br>
> Cc: "Yann Morin" <yann.morin.1998@free.fr>, "Peter Korsgaard" <peter@korsgaard.com>, "Mahyar Koshkouei"
> <mahyar.koshkouei@gmail.com>, "Thomas De Schampheleire" <thomas.de_schampheleire@nokia.com>, "buildroot"
> <buildroot@buildroot.org>, "Arnout Vandecappelle" <arnout@mind.be>
> Sent: Sexta-feira, 4 de janeiro de 2019 6:58:11
> Subject: Re: [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host

> 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 ?

It started when I realized that the trailing slashes in WAF_SITE and
other host packages. Then Arnout said "we need Config.in.host" and I
decided to give it a try. It may be a silly explanation but sometimes
we do things just for fun. :-)

-- 
Carlos Santos (Casantos) - DATACOM, P&D