From: Viswesh S <viswesh_vichu@yahoo.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Remove conf/*.mk from svn
Date: Tue, 5 Aug 2008 21:58:27 -0700 (PDT) [thread overview]
Message-ID: <762580.66617.qm@web31608.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
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 <fzielcke@z-51.de>
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/
[-- Attachment #2: Type: text/html, Size: 2089 bytes --]
next reply other threads:[~2008-08-06 4:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 4:58 Viswesh S [this message]
2008-08-06 14:56 ` Remove conf/*.mk from svn Vesa Jääskeläinen
-- strict thread matches above, loose matches on Subject: below --
2008-07-25 5:17 Linking Viswesh S
2008-07-25 15:18 ` Remove conf/*.mk from svn (was: Re: Linking) Colin D Bennett
2008-07-25 18:41 ` Remove conf/*.mk from svn Christian Franke
2008-07-27 7:17 ` Pavel Roskin
2008-07-27 22:28 ` Christian Franke
2008-07-28 22:43 ` Pavel Roskin
2008-08-05 10:38 ` Marco Gerards
2008-08-05 10:40 ` Marco Gerards
2008-08-05 15:38 ` Vesa Jääskeläinen
2008-08-05 15:48 ` Marco Gerards
2008-08-05 15:55 ` Felix Zielcke
2008-08-05 18:41 ` Javier Martín
2008-08-05 18:51 ` Colin D Bennett
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=762580.66617.qm@web31608.mail.mud.yahoo.com \
--to=viswesh_vichu@yahoo.com \
--cc=grub-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox