public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <cyklonite@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: rfc: the demise of grub:0
Date: Thu, 13 Oct 2016 10:01:17 -0400	[thread overview]
Message-ID: <ff7ea72e-6bae-4c96-7daa-34b619c60b69@gmail.com> (raw)
In-Reply-To: <20161004222416.GA17685@whubbs1.gaikai.biz>

On 10/04/2016 06:24 PM, William Hubbs wrote:
>  
>  This would actually be another reason to get rid of grub-0, if it can't
>  build on one of our profiles, it will more than likely never be fixed
>  upstream because they are now focused on grub-2.x.

grub-0 is 32-bit software. You could build it without multilib but you need
the dependencies like any other package (and link them statically). And there
are other packages on the tree that don't build on all profiles.

>> Another alternative would be simply hard-masking it, but leaving it in 
>> place for those who want it.  It does still work, and I see no evidence 
>> we're removing it due to security issues or breakage.
> 
> We are removing it because upstream has a new version of the software
> and has moved on from this one. For most packages, if foo-1.0 is
> stable, then foo-2.0 comes to stable, after some point we remove foo-1.0
> from the tree.

Grub2 is not really a new version, it's a different product with different
use cases. I don't use grub-0 to boot any of my gentoo boxes but I use it for
some embedded x86 projects so it's convenient to be able build it off the
tree. I remember trying grub2 on one of them a while back and IIRC it more
than doubled the size of the image.

Just my 2 cents worth.

-- 

Fernando Rodriguez


  reply	other threads:[~2016-10-13 13:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 21:59 [gentoo-dev] rfc: the demise of grub:0 William Hubbs
2016-10-03 22:48 ` Matthias Maier
2016-10-04  1:03 ` Michael Orlitzky
2016-10-04  7:45 ` [gentoo-dev] " Jörg Schaible
2016-10-04  8:06   ` Michał Górny
2016-10-04  8:57   ` James Le Cuirot
2016-10-04 13:12   ` Nick Vinson
2016-10-04 20:44 ` Duncan
2016-10-04 22:24   ` William Hubbs
2016-10-13 14:01     ` Fernando Rodriguez [this message]
2016-10-13 14:13       ` Raymond Jennings
2016-10-13 14:21         ` Ian Stakenvicius
2016-10-14 14:22           ` Fernando Rodriguez
2016-10-14 14:25             ` Ian Stakenvicius
2016-10-04 22:04 ` [gentoo-dev] " Dan Douglas
2016-10-04 22:21   ` Mike Gilbert
2016-10-04 22:28   ` William Hubbs
2016-10-05  1:29     ` Kent Fredric
2016-10-05  2:22       ` Rich Freeman
2016-10-05  2:57         ` Kent Fredric
2016-10-05 11:04           ` Rich Freeman
2016-10-05 12:54             ` Kent Fredric
2016-10-05 17:26               ` Patrick McLean

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=ff7ea72e-6bae-4c96-7daa-34b619c60b69@gmail.com \
    --to=cyklonite@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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