From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Pavel Roskin <proski@gnu.org>
Subject: Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe
Date: Sun, 23 Aug 2009 13:03:21 +0200 [thread overview]
Message-ID: <20090823110321.GM4130@thorin> (raw)
In-Reply-To: <1251015769.3612.3.camel@fz.local>
On Sun, Aug 23, 2009 at 10:22:49AM +0200, Felix Zielcke wrote:
> Am Donnerstag, den 20.08.2009, 18:18 -0400 schrieb Pavel Roskin:
> > On Wed, 2009-08-19 at 17:18 +0200, Robert Millan wrote:
> >
> > > The eye candy is nice but not so important. For me, gfxterm should be
> > > default on platforms where it's available, because it implements UTF-8,
> > > which is necessary to support l10n.
> >
> > Fine with me. Just please don't rely on existence of modules.
> >
>
> Here's now a patch which moves the check for vbe.mod from 00_header to
> grub-mkconfig and enables gfxterm if it's found.
Just a min, I think Pavel's concern about reliing on existence of modules was
resolved with this commit:
2009-08-21 Pavel Roskin <proski@gnu.org>
* Makefile.in (install-local): When checking if a file is in the
build directory, use "test -e" to detect symlinks.
* Makefile.in (install-local): Remove all files in
$(DESTDIR)$(pkglibdir) before installing new files there.
Pavel, if you could confirm that you're ok with checking for module
existance, maybe Felix' patch can be made simpler.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-23 11:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 9:43 grub-mkconfig fails on every non i386-pc because of gfxterm/vbe Felix Zielcke
2009-06-03 20:55 ` Pavel Roskin
2009-06-03 22:11 ` Felix Zielcke
2009-06-09 20:24 ` Felix Zielcke
2009-06-12 1:09 ` Pavel Roskin
2009-08-14 6:44 ` Felix Zielcke
2009-08-18 17:58 ` Pavel Roskin
2009-08-18 18:09 ` Felix Zielcke
2009-08-18 18:25 ` Michal Suchanek
2009-06-11 16:09 ` Vladimir 'phcoder' Serbinenko
2009-07-22 11:04 ` Felix Zielcke
2009-08-18 17:44 ` Pavel Roskin
2009-08-18 17:53 ` Vladimir 'phcoder' Serbinenko
2009-08-18 18:11 ` Pavel Roskin
2009-08-19 15:18 ` Robert Millan
2009-08-20 22:18 ` Pavel Roskin
2009-08-20 22:45 ` Vladimir 'phcoder' Serbinenko
2009-08-21 11:14 ` Michal Suchanek
2009-08-23 8:22 ` Felix Zielcke
2009-08-23 11:03 ` Robert Millan [this message]
2009-08-25 19:35 ` Robert Millan
2009-08-25 19:47 ` Felix Zielcke
2009-09-11 21:54 ` Pavel Roskin
2009-09-12 12:58 ` Robert Millan
2009-09-12 13:17 ` Felix Zielcke
2009-09-12 20:44 ` Michal Suchanek
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=20090823110321.GM4130@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=proski@gnu.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.