From: Tom Rini <trini@embeddedalley.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] grub: allow menu.lst to be overridden using GRUB_CONFIG_PACKAGE.
Date: Wed, 6 May 2009 16:40:11 -0700 [thread overview]
Message-ID: <20090506234010.GS7973@smtp.west.cox.net> (raw)
In-Reply-To: <20090506223838.GA15339@denix.org>
On Wed, May 06, 2009 at 06:38:38PM -0400, Denys Dmytriyenko wrote:
> On Wed, May 06, 2009 at 03:55:57PM -0400, Michael Smith wrote:
> > If GRUB_CONFIG_PACKAGE is set, don't ship menu.lst with grub. Instead,
> > RRECOMMEND the config package. This allows overlays to override menu.lst
> > in a separate package, rather than copying the whole grub package into
> > the overlay.
>
> It was discussed many times here - no USE flags in OE. You'll end up with 2
> grub packages of the same name but with different contents - with menu.lst
> and without.
> One of the recent discussions on this topic:
> http://thread.gmane.org/gmane.comp.handhelds.openembedded/22715/focus=22731
I need to find time to argue for USE flags sometime. In short 'tho, you
only end up with 2 grub packages that differ if, well, you want them to.
Distros (Angstrom) that let people install stuff on the system from
feeds should do something like:
### DO NOT CHANGE ANY OF THE FOLLOWING IF YOU INTEND TO PUBLISH YOUR
### PACKAGES. DOING SO WILL BREAK PEOPLE.
USE_FLAG_1 := ...
USE_FLAG_2 := ...
And distros that really want to USE (or not USE) something can set them
differently, and we don't end up with N permutations of recipes that
people have to mind when fixing things nor forking for their own use the
recipes and stripping things out. It's really two sides of the same
coin.
> One way to solve it would be to always have menu.lst as a separate package and
> then replace it with your own from the overlay.
>
> > SRC_URI = "ftp://alpha.gnu.org/gnu/grub/grub-${PV}.tar.gz \
Unrelated, this should be ${GNU_MIRROR}/grub/grub-${PV}.tar.gz
--
Tom Rini
next prev parent reply other threads:[~2009-05-06 23:46 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 [this message]
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
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=20090506234010.GS7973@smtp.west.cox.net \
--to=trini@embeddedalley.com \
--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.