From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: Overriding package config files in OE
Date: Fri, 02 Nov 2007 07:08:51 -0400 [thread overview]
Message-ID: <472B0543.5070203@balister.org> (raw)
In-Reply-To: <f96d234e0711011307y6d07604dg110d5c443ecb0e8f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Cliff Brake wrote:
> Another approach I've been thinking about is to figure out a way for
> bitbake to use <files> from a tree outside the main OE tree. One
> possibility is for bitbake to pull <files> as well as bb files from a
> high priority bbcollections tree, even though the bb remains in the
> main OE tree. This probably totally breaks the way bitbake works, but
I think that having an overlay set up as a high priority collection does
work. Steve S. uses one for his gumstix project. I like this method
because I can easily find all the local changes he makes and see if they
need to move back into .dev.
A local overlay lets you change the version of .dev underneath as
needed, without moving changes across branches. Combined with sane
source rev/dates, I believe this gives the people supporting product a
sane build/support environment.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2007-11-02 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 16:49 Overriding package config files in OE shanevolpe
2007-11-01 20:07 ` Cliff Brake
2007-11-02 11:08 ` Philip Balister [this message]
2007-11-02 14:22 ` Cliff Brake
2007-11-02 16:33 ` Koen Kooi
2007-11-10 13:04 ` Leon Woestenberg
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=472B0543.5070203@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.