Comment 0 for bug 1373137

I noticed this when installing ppc64el, as boot would fail. It would fail because no /boot/grub/grub.cfg existed.
I'm not entirely sure when we need to run update-grub.

I know that the 'install_grub' was choosing to *not* run update-grub because sometimes dpkg-reconfigure would do the same thing, and that was a slow operation.

Its possible there are more complex symantics involved than I understood. But we were not running 'update-grub' in order to save some time.

Basically, as input to 'install_grub', we have:
  * the target to install to (/dev/sda1 or /dev/sda)
  * the dpkg arch
  * the name of the package to 'dpkg-reconfigure' (derived from the dpkg arch and whether or not to use uefi).
    we dpkg-reconfigure because we may change the GRUB_CMDLINE_LINUX_DEFAULT to include additional options such as console=

From my memory, it seemed like on amd64 and i386, running 'dpkg-reconfigure grub-pc' would end up running update-grub. I then chose not to run update-grub because it was slow.

Colin, Is there some simple logic that I can use to determine when running update-grub is needed?