Re: refind: account for btrfs setups when generating manual stanzas

[slymattz <slymattz@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

New comment by slymattz on void-packages repository

https://github.com/void-linux/void-packages/pull/48906#issuecomment-1966683233

Comment:
@sgn maintainer ping

Although initially my PR focused on btrfs setups, the simple changes proposed by @ahesford in both _/etc/default/refind-kernel-hook.conf_ and _/etc/kernel.d/post-install/50-refind_ are more universal as they can save a lot of trouble when installing  Void manually (either through chroot from a different distribution or xchroot from Void). My argument is that these ways of installation are officially documented in Void Linux Docs (so refind could include the appropriate changes). On top of that, the part where `mkfs.ext4` is listed (see https://docs.voidlinux.org/installation/guides/chroot.html#prepare-filesystems) doesn't mention the necessity to use `-L "Void Linux"` for painless installation of refind. Even if it did mention this detail, I believe REFIND_CONF, REFIND_LABEL and REFIND_BOOT_PREFIX would have to be tweaked if we were to retain the partition-and-filesystem setup proposed in Docs (see https://docs.voidlinux.org/installation/guides/chroot.html#configure-fstab).

P.S. the first workflow run failed for aarch64 (both glibc and musl) but I ran a cross-compilation of aarch64-glibc on the upstream tree yesterday and it succeeded this time so the compilation errors must've had to do with some dependency incompatibilities at the time or something. That's my guess. 

What do y'all think?