From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] [RFC] use alternatives to manage initramfs regeneration
Date: Wed, 14 Sep 2022 19:05:35 +0200 [thread overview]
Message-ID: <20220914170535.9QnFEj2-K7lhpp2HhWSMA9lf3dwN-coy_0hkK-Tp-rk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39284@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
New review comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/39284#discussion_r971085307
Comment:
Yes and no. I was torn about adding an alternative here because it doesn't conflict in the same way as mkinitcpio/dracut, but presumably somebody interested in spitting out a UEFI bundle doesn't care about a separate initramfs in `/boot`. We could skip the alternative here and just install the hooks as they are now, or a user who wishes for both a separate initramfs and a UEFI bundle could manually link to the new hooks in `/usr/libexec`.
Motivation for this comes from https://github.com/void-linux/void-packages/pull/39282.
next prev parent reply other threads:[~2022-09-14 17:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 16:00 [PR PATCH] " ahesford
2022-09-14 16:25 ` CameronNemo
2022-09-14 16:38 ` [PR REVIEW] " CameronNemo
2022-09-14 17:05 ` ahesford [this message]
2022-09-14 17:07 ` ahesford
2022-09-14 19:15 ` [PR REVIEW] " dmarto
2022-09-15 1:29 ` [PR PATCH] [Updated] " ahesford
2022-09-15 1:29 ` [PR REVIEW] " ahesford
2022-09-15 10:26 ` classabbyamp
2022-09-18 17:55 ` [PR PATCH] [Updated] " ahesford
2022-09-18 18:39 ` ahesford
2022-09-18 18:49 ` ahesford
2022-09-18 18:57 ` ahesford
2022-09-18 18:58 ` ahesford
2022-09-19 8:19 ` thypon
2022-09-19 9:23 ` classabbyamp
2022-09-19 11:04 ` ahesford
2022-09-19 20:33 ` classabbyamp
2022-09-26 12:17 ` [PR PATCH] [Merged]: " ahesford
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=20220914170535.9QnFEj2-K7lhpp2HhWSMA9lf3dwN-coy_0hkK-Tp-rk@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).