From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Overriding package config files in OE
Date: Fri, 02 Nov 2007 17:33:04 +0100 [thread overview]
Message-ID: <472B5140.6060002@student.utwente.nl> (raw)
In-Reply-To: <f96d234e0711020722i2305f16et15f2b5b122c94aea@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cliff Brake schreef:
> On 11/2/07, Philip Balister <philip@balister.org> wrote:
>> 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.
>
> I was referring to the case where I only put the files directory in
> the overlay -- not the entire recipe directory. I have not tried this
> lately and will do so the next time I get a chance.
>
>> 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.
>
> Agreed. I use overlays a lot as well and they work great -- I would
> just like to avoid having to copy the entire recipe + the files
> directory -- for example just to make a small change in
> /etc/network/interfaces. If you copy the entire recipe directory,
> diff'ing is easy initially, but several months down the road it is
> very difficult to figure out what you changed.
You could also do it the openmoko way by defining extra overrides and
using those in FILESPATH.
regards,
Koen
- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHK1FAMkyGM64RGpERAuFpAJ44e/KObKpHYwvmXrLyqNy4o+9VDgCfRUQk
syve1LMsa+yXbjUdrE4NfsQ=
=eU2C
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-11-02 16:33 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
2007-11-02 14:22 ` Cliff Brake
2007-11-02 16:33 ` Koen Kooi [this message]
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=472B5140.6060002@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--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.