Hi,

after hearing in passing by that grub is also available as monolithic
version that doesn't need that huge modules directory that gets so
easily out of sync, I tried to understand what the grub packages for
amd64-efi contain.

I stumbled over the package description for grub-efi-amd64,
grub-efi-amd64-bin, and grub-efi-amd64-unsigned claim to be "built for
use with the EFI-AMD64 architecture, as used by Intel Macs (unless a
BIOS interface has been activated)".

Apple has stopped making Intel Macs like five years ago, and the vast
majority of machine sold today boot with those packages.

I think the description should be more like "...has been built for
use with the vast majority of machines with the amd64 architecture,
booting via UEFI firmware. This applies to most machines sold after
2015, unless the compatibility layer to the obsolete PC BIOS interface
was deliberately enabled."

After this change was done, I'd like to recommend more rewording of the
description. For example, it should be in the package description that
grub-efi-amd64-bin contains the modules and not the actual bootmanager,
while the grub-efi-amd64-signed package contains the actual bootmanager
(that needs the modules, right?). The grub-efi-amd64-unsigned contains
grubx64.efi files in a "monolithic" subdirectory, so those images do not
need the modules, do they? and if they dont need the modules, why is the
monolithic grub not available signed? Otoh, the file sizes suggest that
the monolithic/grubx86.efi doesn't contain significantly more code than
the files in the -signed package.

This is all totally confusing.

I guess the situation in the arm64 world isn't much better, I have
successfully booted a Raspberry Pi with a (truly?) monolithic grub that
doesn't need the modules at all.

Please, consider improving the docs and descriptions.

Greetings
Marc