From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Removing autogenerated files from svn
Date: Wed, 15 Apr 2009 00:35:00 +0900 [thread overview]
Message-ID: <200904150035.00910.okuji@enbug.org> (raw)
In-Reply-To: <20090413143042.GH12170@thorin>
On Monday 13 April 2009 23:30:42 Robert Millan wrote:
> On Sun, Apr 12, 2009 at 04:54:21PM -0400, Pavel Roskin wrote:
> > On Sun, 2009-04-12 at 11:29 -0700, Colin D Bennett wrote:
> > > phcoder wrote on Sunday 12 April 2009:
> > > > Hello, we all know how annoying are these autogenerated files. We
> > > > could remove it. The main argument against it is that people will not
> > > > be able to compile without installing a lot of developement tools. It
> > > > changes nothing for the users wanting to modify the code. So I
> > > > propose to remove these files but in compensation setup a nightly
> > > > build server. I'm ready to supply all necessary scripts to create a
> > > > source tar.gz with autogenerated files, binary tar.gz and rescue iso
> > > > for all platforms where applicable.
> > >
> > > Great idea. I'd love to see this happen.
> >
> > Me too.
>
> Me too.
>
> Okuji, can we agree on it this time? It's annoying for most people, and
> release tarballs can include the autogenerated files, so the ruby
> dependency is not a problem for end users.
Well, it was not only about ruby, but also about autoconf. Anyway, if someone
updates the INSTALL file appropriately, I don't object.
Regards,
Okuji
next prev parent reply other threads:[~2009-04-14 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 11:47 Removing autogenerated files from svn phcoder
2009-04-12 18:29 ` Colin D Bennett
2009-04-12 20:54 ` Pavel Roskin
2009-04-13 14:30 ` Robert Millan
2009-04-14 15:35 ` Yoshinori K. Okuji [this message]
2009-04-14 16:12 ` Felix Zielcke
2009-04-14 13:50 ` Jordi Mallach
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=200904150035.00910.okuji@enbug.org \
--to=okuji@enbug.org \
--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.