Arch Linux

Description:

The GRUB consist of two independent sections:
* GRUB bootloader in /boot/grub and system disk areas, working without any OS and without any packages.
* Files and utils for install/configure, works under Arch Linux, and provides by "grub" package.

The "grub" package provides files ant utils, but doesn't install the bootloader.
With small, but very bad exeprion: "grub.cfg" file. This file is an important part of GRUB bootloader, but provides by "grub" package with bootloader-only (not /usr/) path: /boot/grub/grub.cfg

Moreover, the current "grub" package contains absolutely unworkable and useless version of this file (wrong UUID's, for example), despite the fact that when you install the package immediately generating significantly more actual version.
grub.install:
grub-mkconfig -o /boot/grub/grub.cfg.example

Possible situations in which the operation with package "grub" may break down the next booting the system:

* When uninstalling "grub" package (but not the bootloader!), the existing working GRUB bootloader file "grub.cfg" is automatically moved to "grub.cfg.pacsave", because same time it is a part of the package.

* When installing of "grub" package, the existing working "grub.cfg" may be raplaced by NOT TESTED "grub.cfg.pacsave" file, if it will by found in /boot/grub/
grub.install:
if [ -f /boot/grub/grub.cfg.pacsave ]; then
echo "Copying /boot/grub/grub.cfg.pacsave to /boot/grub/grub.cfg"
install -D -m0644 /boot/grub/grub.cfg.pacsave /boot/grub/grub.cfg
fi

The fixes can resolve that collision and improve usability of "grub" package:

1) In package files: rename "grub.cfg" to "grub.cfg.default"
2) New "grub.install" script (see attachment). It can write to grub.cfg ONLY if it NOT exists, and have 3 candidats to grub.cfg (in priority order): grub.cfg.pacsave, grub.cfg.auto (generated) and grub.cfg.default (from package).