From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Cc: Fabio Berton <fabio.berton@ossystems.com.br>
Subject: Re: [meta-oe][PATCH] fio: Remove --disable-static from EXTRA_OECONF
Date: Sun, 21 Feb 2016 22:44:48 +0000 [thread overview]
Message-ID: <1456094688.28376.178.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQfOYEfP=h8U1_Q7FXLUKuqvZ=o967=5vSVf3Phqag7yyA@mail.gmail.com>
On Sun, 2016-02-21 at 11:47 +0100, Martin Jansa wrote:
> What's the advantage of more global .inc file?
In OE-Core it started as a standalone experiment which made sense as a
separate .inc as we've done with some other things of this nature. I
thought it was going to take longer to work through and establish.
Having looked at the effect, I decided to adopt it for poky. At this
point I suspect marking up the recipes is the best way to do things.
I'd note that if we had a way to know if a recipe was really autotools
or just acts a bit like it, it would help a lot...
> IMHO it's only increasing chances for conflicts when merging/cherry
> -picking.
I think the central class did make sense for an initial evaluation of
this but probably not going forward...
Cheers,
Richard
next prev parent reply other threads:[~2016-02-21 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 17:19 [meta-oe][PATCH] fio: Remove --disable-static from EXTRA_OECONF Fabio Berton
2016-02-18 20:43 ` Christopher Larson
2016-02-19 13:23 ` Otavio Salvador
2016-02-21 10:30 ` Richard Purdie
2016-02-21 10:47 ` Martin Jansa
2016-02-21 22:44 ` Richard Purdie [this message]
2016-02-22 9:52 ` Burton, Ross
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=1456094688.28376.178.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fabio.berton@ossystems.com.br \
--cc=openembedded-devel@lists.openembedded.org \
/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.