From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/1]: profiles/use.desc: add efi global use flag
Date: Fri, 14 Jul 2023 13:11:46 -0400 [thread overview]
Message-ID: <CAJ0EP411N1qwcbk6cfEH5-+guLjhgn-P-GMAdJndnoKR1gUJ8g@mail.gmail.com> (raw)
In-Reply-To: <87zg3yzwpb.fsf@gentoo.org>
On Fri, Jul 14, 2023 at 5:07 AM Sam James <sam@gentoo.org> wrote:
>
>
> Andrew Ammerlaan <andrewammerlaan@gentoo.org> writes:
>
> > Hi all,
> >
> > Currently we have 7 packages defining the efi flag and an additional 2
> > defining the uefi flag. These flags do the same thing, add support for
> > (U)EFI booting. I therefore propose we introduce efi as a new global
> > flag and later rename the uefi flag to efi in sys-apps/fwupd and
> > sys-apps/ipmicfg.
> >
> > I don't have a strong preference between the efi or uefi flags, but
> > since a majority of the packages has chosen efi I suggest we go with
> > that.
>
> Let's do USE=uefi please - UEFI is the modern name for it, and EFI is
> legacy. I'd like to avoid another USE=ssl situation (where we're
> stuck with it forever given we have no mechanism for USE flag renames,
> despite the fact that it's really TLS now).
Any thoughts on grub_platforms_efi-32 and grub_platforms_efi-64?
If we want to rename USE flags, I would probably take the opportunity
to eliminate the GRUB_PLATFORMS USE_EXPAND altogether.
next prev parent reply other threads:[~2023-07-14 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 8:53 [gentoo-dev] [PATCH 1/1]: profiles/use.desc: add efi global use flag Andrew Ammerlaan
2023-07-14 9:05 ` David Seifert
2023-07-14 9:11 ` Andrew Ammerlaan
2023-07-14 9:07 ` Sam James
2023-07-14 17:11 ` Mike Gilbert [this message]
2023-07-14 18:21 ` Andrew Ammerlaan
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=CAJ0EP411N1qwcbk6cfEH5-+guLjhgn-P-GMAdJndnoKR1gUJ8g@mail.gmail.com \
--to=floppym@gentoo.org \
--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