On 2018-12-08 13:45, mar77i via arch-general wrote:
> For the kernel we run mkinitcpio. So there shouldn't be a real reason why we
> shouldn't run grub-mkconfig >/${main_grub_dir}/grub.cfg for grub. That being
> said, the path is /boot/grub.cfg for me, so I'm not sure how we'd get the
> installfile to figure out where to output its output.
>
> One key difference is that the output of mkinitcpio are binary files, whereas
> grub.cfg is a text file, and maybe operators would like to modify that file
> after it's generated? So one could make a case that the install file should
> in fact keep its hands off grub.cfg entirely.
Right, grub.cfg can quite easily be written by hand.
Also, there is (usually?) no necessity to change the grub.cfg after a
grub update. I doubt even that the grub-mkconfig output changes (notably).
