From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Remove conf/*.mk from svn
Date: Tue, 05 Aug 2008 20:41:53 +0200 [thread overview]
Message-ID: <1217961713.14674.34.camel@localhost> (raw)
In-Reply-To: <87sktjcvit.fsf@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
El mar, 05-08-2008 a las 17:48 +0200, Marco Gerards escribió:
> Vesa Jääskeläinen <chaac@nic.fi> writes:
>
> > Marco Gerards wrote:
> >> Colin D Bennett <colin@gibibit.com> writes:
> >>> I think we should remove conf/*.mk from the Subversion repository. If
> >>> people are going to be developing on GRUB and checking out svn
> >>> branches, then I think it's fine to require them to have Ruby. For
> >>> released tarballs that we expect non-developers to use, we just need to
> >>> generate the *.mk files and include them in the tarball.
> >>
> >> I do not have problems with this. Besides this, it will stop people
> >> from sending in patches with .mk changes in it :-)
> >
> > I think Okuji's objection is based on fact that it makes it harder for
> > people to compile from sources. Now what if we would generate those
> > files when making a release? Of course this should be enabled to
> > script/makefile to make it automatically so it is not forgotten ;)
>
> Right. Just to be clear, personally I didn't have these objections
> but Okuji has.
>
> Actually, since ruby is required to generate these files, I guess we
> can better keep the .mk files.
Why not rewrite genmk.rb in a more common language (i.e. with an
interpreter more commonly found in stock GNU installs) like Python or
Perl?
Habbit
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-08-05 18:39 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 ` Remove conf/*.mk from svn Felix Zielcke
2008-08-05 18:41 ` Javier Martín [this message]
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=1217961713.14674.34.camel@localhost \
--to=lordhabbit@gmail.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