From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bob Cochran <yocto@mindchasers.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Questioning FILESOVERRIDES implied precedence in setting FILESPATH...
Date: Mon, 01 Dec 2014 16:56:44 +0000 [thread overview]
Message-ID: <1417453004.15614.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <547C0400.3010706@mindchasers.com>
On Mon, 2014-12-01 at 01:00 -0500, Bob Cochran wrote:
> In poky master, FILESOVERRIDES is constructed as follows:
>
> "${TRANSLATED_TARGET_ARCH}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}"
>
> For my current build, I get:
>
> FILESOVERRIDES="powerpc:custom-machine:e500v2:qoriq-ppc:poky"
>
> FILESPATH is built by calling base_set_filespath(), which is in
> utils.bbclass
>
> This function constructs FILESPATH in such a way that the distro folder
> ("poky") comes before the other overrides ( precedence is applied right
> to left using FILESOVERRIDES )
>
> I see that there was a patch to reverse the ordering back in Oct of 2013
> (0bd63125c3b44) to make sure MACHINE overrides had precedence over
> platform specific overrides. However, I'm wondering if the intent was
> to have the distro override both. This doesn't make sense to me, so
> please clarify whether this is correct. If it is, please explain why
> distro gets a higher precedence over machine.
It is intentional, the concept is that the distro is the ultimate
authority on configuration and it should be able to override anything,
including machine specific choices. I would agree that can work well in
some cases and less well in others.
Cheers,
Richard
next prev parent reply other threads:[~2014-12-01 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 6:00 Questioning FILESOVERRIDES implied precedence in setting FILESPATH Bob Cochran
2014-12-01 16:56 ` Richard Purdie [this message]
2014-12-01 17:54 ` Bob Cochran
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=1417453004.15614.30.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=yocto@mindchasers.com \
--cc=yocto@yoctoproject.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.