From: Andrew Ammerlaan <andrewammerlaan@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 20:21:41 +0200 [thread overview]
Message-ID: <f2d8a741-3238-ddf8-8398-2660161d932a@gentoo.org> (raw)
In-Reply-To: <CAJ0EP411N1qwcbk6cfEH5-+guLjhgn-P-GMAdJndnoKR1gUJ8g@mail.gmail.com>
On 14/07/2023 19:11, Mike Gilbert wrote:
> 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.
>
For grub specifically there is another thing to consider. Currently
emerging grub does not actually build an efi executable, this (I think)
is done when you 'grub-install'. This is unfortunate because that makes
it the only bootloader that you can't conveniently sign with
secureboot.eclass.
I briefly looked into the problem and there is 'grub-mkstandalone' which
could be used to generate (and then sign) a grub efi executable. But how
this would then work with 'grub-install' I do not know. I don't use grub
myself, but maybe someone who does can look into this.
Best regards,
Andrew
prev parent reply other threads:[~2023-07-14 18:21 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
2023-07-14 18:21 ` Andrew Ammerlaan [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=f2d8a741-3238-ddf8-8398-2660161d932a@gentoo.org \
--to=andrewammerlaan@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