From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Remove conf/*.mk from svn
Date: Tue, 05 Aug 2008 17:55:43 +0200 [thread overview]
Message-ID: <1217951743.23608.6.camel@fz.local> (raw)
In-Reply-To: <87sktjcvit.fsf@xs4all.nl>
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 :)
next prev parent reply other threads:[~2008-08-05 15:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 5:17 Linking Viswesh S
2008-07-25 5:35 ` Linking Pavel Roskin
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-07-25 20:43 ` Remove conf/*.mk from svn (was: Re: Linking) Robert Millan
2008-07-31 20:18 ` Yoshinori K. Okuji
2008-08-05 10:40 ` Remove conf/*.mk from svn Marco Gerards
2008-08-05 15:38 ` Vesa Jääskeläinen
2008-08-05 15:48 ` Marco Gerards
2008-08-05 12:02 ` Seeking for the start administrador02032
2008-08-05 15:55 ` Felix Zielcke [this message]
2008-08-05 18:41 ` Remove conf/*.mk from svn Javier Martín
2008-08-05 18:51 ` Colin D Bennett
-- strict thread matches above, loose matches on Subject: below --
2008-08-06 4:58 Viswesh S
2008-08-06 14:56 ` Vesa Jääskeläinen
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=1217951743.23608.6.camel@fz.local \
--to=fzielcke@z-51.de \
--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 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.