From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] grub: allow menu.lst to be overridden using GRUB_CONFIG_PACKAGE.
Date: Sat, 16 May 2009 15:03:59 -0400 [thread overview]
Message-ID: <20090516190358.GA2564@denix.org> (raw)
In-Reply-To: <b6ebd0a50905151521v725c075dxabc2e2f20c51a327@mail.gmail.com>
On Fri, May 15, 2009 at 03:21:03PM -0700, Chris Larson wrote:
> On Thu, May 7, 2009 at 12:03 PM, Michael Smith <msmith@cbnco.com> wrote:
> [snip]
> > My grub_0.97.bb could reference file://some.patch in its SRC_URI and bitbake
> > could look in the next COLLECTION after failing to find it in the local one.
> > In fact, I wouldn't even really need a bbfile in the overlay; just having
> > files/menu.lst in the overlay could be enough to replace it. I guess this
> > might just require some fudging to how FILESPATH is set up in base.bbclass.
>
> This piece is covered relatively easily by manipulating FILESPATHBASE.
>
> > Second, if a recipe could include a recipe of the same name and let bitbake
> > search for it in the next COLLECTION, overlay packages could get a lot
> > smaller. Say I need to add a private patch to grub -- my overlay
> > grub_0.97.bb, if I had one, could just look like this:
>
> This piece I believe I have a solution for. I just wrote a 15 line
> .inc file that when loaded in a .conf, automatically searches any
> recipe's FILESPATH for an amend.inc, and if it exists, parses that in
> after the recipe itself is parsed, so you can amend the recipe with
> tweaks and things at the end of the parse. So this coupled with the
> aforementioned FILESPATHBASE alterations and you should be able to
> supply overlay specific changes to a recipe without having to copy the
> recipe itself into the overlay.
Chris,
You are on the roll! This is another very welcomed feature for anyone who
manages overlays. Thanks!
--
Denys
next prev parent reply other threads:[~2009-05-16 19:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 19:55 [PATCH 1/2] Remove unused grub-0.93 Michael Smith
2009-05-06 19:55 ` [PATCH 2/2] grub: allow menu.lst to be overridden using GRUB_CONFIG_PACKAGE Michael Smith
2009-05-06 22:38 ` Denys Dmytriyenko
2009-05-06 23:40 ` Tom Rini
2009-05-07 6:45 ` Phil Blundell
2009-05-07 19:03 ` Michael Smith
2009-05-15 22:21 ` Chris Larson
2009-05-16 19:03 ` Denys Dmytriyenko [this message]
2009-05-07 19:47 ` Denys Dmytriyenko
2009-05-07 18:24 ` Michael Smith
2009-05-07 18:27 ` [PATCH 1/3] Remove unused grub-0.93 Michael Smith
2009-05-07 18:27 ` [PATCH 2/3] grub: use ${libdir}, not /usr/lib Michael Smith
2009-05-07 18:27 ` [PATCH 3/3] grub: split menu.lst into a separate package, grub-config Michael Smith
2009-05-07 19:02 ` Chris Larson
2009-05-07 22:19 ` Michael Smith
2009-05-07 22:37 ` manual missing dependencies section? Rich Pixley
2009-05-07 23:59 ` Cliff Brake
2009-05-07 19:52 ` [PATCH 3/3] grub: split menu.lst into a separate package, grub-config Denys Dmytriyenko
2009-05-07 19:18 ` [PATCH 2/3] grub: use ${libdir}, not /usr/lib Leon Woestenberg
2009-05-07 19:26 ` Otavio Salvador
2009-05-07 18:36 ` Phil Blundell
2009-05-07 19:58 ` Michael Smith
2009-05-07 20:02 ` Otavio Salvador
2009-05-07 20:05 ` Leon Woestenberg
2009-05-07 22:24 ` Michael Smith
2009-05-08 1:35 ` Otavio Salvador
2009-05-08 19:15 ` Leon Woestenberg
2009-05-09 0:46 ` Otavio Salvador
2009-05-12 2:53 ` Michael Smith
2009-05-12 2:53 ` [PATCH] Remove unused grub-0.93 Michael Smith
2009-05-12 2:53 ` [PATCH] grub: Split the grub-install script and friends into a separate package Michael Smith
2009-05-12 3:02 ` Tom Rini
2009-05-12 3:18 ` Michael Smith
2009-05-12 4:13 ` Tom Rini
2009-05-07 20:02 ` [PATCH 2/3] grub: use ${libdir}, not /usr/lib Graeme Gregory
2009-05-07 19:25 ` [PATCH 1/3] Remove unused grub-0.93 Otavio Salvador
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=20090516190358.GA2564@denix.org \
--to=denis@denix.org \
--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.