From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>
Subject: Re: [PATCH] Give coreutils a chance to build the df utility
Date: Wed, 26 Oct 2011 15:01:55 +0100 [thread overview]
Message-ID: <1319637716.22985.368.camel@phil-desktop> (raw)
In-Reply-To: <CAKZ=5EUxO=fe+6p5qx4n5Y5_r1GQ+mokXOQhnuNgLbpx7Z4Heg@mail.gmail.com>
On Wed, 2011-10-26 at 14:58 +0100, Julian Pidancet wrote:
> On Wed, Oct 26, 2011 at 2:59 AM, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
> > On Mon, Oct 24, 2011 at 8:18 PM, Julian Pidancet
> > <julian.pidancet@gmail.com> wrote:
> >> +do_configure_prepend () {
> >> + export fu_cv_sys_stat_statfs2_bsize=yes
> >
> > I'm asking out of curiosity.. why don't these go in meta/site/common instead?
>
> To be honest, I ignored the very existence of this file. Is this
> globally applied to all the recipes ? Isn't there a risk of breaking
> other packages by doing this ?
A small risk, yes. On the other hand, by hardcoding one particular
value in the recipe, there is a risk that it might be the wrong answer
for some target systems. Whereas the site files are, intentionally,
target and OS specific.
p.
prev parent reply other threads:[~2011-10-26 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 1:18 [PATCH] Give coreutils a chance to build the df utility Julian Pidancet
2011-10-26 1:59 ` McClintock Matthew-B29882
2011-10-26 13:58 ` Julian Pidancet
2011-10-26 14:01 ` Phil Blundell [this message]
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=1319637716.22985.368.camel@phil-desktop \
--to=philb@gnu.org \
--cc=B29882@freescale.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox