Hi,
I have a small suggestion.
Why cant we document in a small file, the procedures, or the dont's while
adding modules or modifying grub2.A FAQ file may be.
That will help us in the long run.
Viswesh
----- Original Message ----
From: Felix Zielcke <[EMAIL PROTECTED]>
To: The development of GRUB 2 <grub-devel@gnu.org>
Sent: Tuesday, 5 August, 2008 9:25:43 PM
Subject: Re: Remove conf/*.mk from svn
Am Dienstag, den 05.08.2008, 17:48 +0200 schrieb Marco Gerards:
>
> Actually, since ruby is required to generate these files, I guess we
> can better keep the .mk files.
>
Just a little note from me:
The Debian package build depends already on ruby so this won't be a
problem for all Debian guys and especially not for Robert or me.
On Debian/Ubuntu you can just use 'apt-get build-dep grub2' and it
installs every package for you which you need to build grub2 so ruby
will be always needed/installed for the Debian package.
But well Debian isn't the only distribution and I don't know how others
deal with grub2 :)
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Download prohibited? No problem. CHAT from any browser, without download.
Go to http://in.webmessenger.yahoo.com/_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
