After moving my main system’s (XFCE) EFI partition to /boot, I’m in the process of doing the same with my test DE VMs. No problems with KDE or Cinnamon. Now I’m trying to do a clean install with LXQT, selecting /boot as FAT32 with the boot flag, same as I’ve done on every EOS system I’ve built. The installer complains that I’m not using /boot/efi, but I politely ignored this warning.
After the install is complete - no errors shown, but I wasn’t watching the console log - I rebooted to a system that did not have a Grub entry in EFI installed. I manually installed Grub via arch-chroot and the system came up fine.
Is this behavior normal? Since Arch recommends using /boot for EFI, why doesn’t EOS?
I am not sure why it wouldn’t work without looking at the code.
One easy solution would be to edit /etc/calamares/modules/partition.conf before launching the installer and change the EFI path near the top of the file.
That being said, mounting your ESP at /boot when using grub works but it is a very strange thing to do. It is also not the best choice from my perspective. I can’t think of any advantage, only disadvantages.
Are you sure that documentation isn’t intended for doing systemd-boot installs, not grub?