All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] enable buildable targets by default
Date: Wed, 22 Jul 2009 19:02:52 +0200	[thread overview]
Message-ID: <20090722170252.GB8706@thorin> (raw)
In-Reply-To: <1247957689.3416.74.camel@mj>

On Sat, Jul 18, 2009 at 06:54:49PM -0400, Pavel Roskin wrote:
> On Sat, 2009-07-18 at 23:38 +0200, Vladimir 'phcoder' Serbinenko wrote:
> 
> > > I fully agree.  The idea with my proposal (we talked this on IRC, I think)
> > > was to simplify things, so I proposed that we enable everything so we don't
> > > have to provide flags, etc.
> > The main pro was to avoid frequent breakage as we experienced with grub-emu.
> 
> I just use a script to build grub for all supported platforms with all
> supported options.  It's quite good for finding such errors.  As it
> stands now, there are no errors and no warnings.  But it took a while to
> fix everything.
> 
> I think we should eventually revert to not building debug tools by
> default.

Your script can detect regressions once they're committed, but enabling
them by default helps prevents them from being committed in first place.  I
think it's an advantage.

> > > I prefer if we got rid of the flags, or at least most of them (lumping them
> > > together with a flag to disable debug tools or so),
> 
> I agree.  grub-emu, grub-fstest and efiemu are debug tools.  Neither is
> needed for normal operation on any platform.

I think efiemu is needed for some loaders.  It's not a debug tool AFAIK.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-07-22 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 13:34 [PATCH] enable buildable targets by default Vladimir 'phcoder' Serbinenko
2009-07-16 16:39 ` Vladimir 'phcoder' Serbinenko
2009-07-17  0:37   ` Pavel Roskin
     [not found]     ` <d7ead6de0907170221h1a204f75ucca48e46c1ff3611@mail.gmail.com>
2009-07-17 14:49       ` Pavel Roskin
2009-07-18 17:55         ` Robert Millan
     [not found]           ` <d7ead6de0907181141n170ec55fueb9d0dccc365cdf3@mail.gmail.com>
2009-07-18 21:38             ` Vladimir 'phcoder' Serbinenko
2009-07-18 22:54               ` Pavel Roskin
2009-07-22 17:02                 ` Robert Millan [this message]

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=20090722170252.GB8706@thorin \
    --to=rmh@aybabtu.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 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.