On Wed, Jun 20, 2012 at 12:42 PM, Adam Williamson <awilliam@redhat.com> wrote:
As I understood it, the latest version of the proposal involves havinggrubby simply call grub2-mkconfig when it is dealing with grub2. So the
rest of the 'stack' doesn't change at all.
Well, the way I see it, that's the solution to the _current_ biggest
problem we have with grubby/grub2 (it completely nerfing the nested
format that mkconfig prefers to generate at present). But I see that
specific problem as only a symptom of a bigger issue, which is that
upstream currently feels perfectly free to make drastic changes to the
grub config file format at any time, in stark contrast to how things
were with grub-legacy, where there was a very stable format we could
rely on. I feel like, if we stick with grubby, we're kind of stuck in a
game of whack-a-mole at least until upstream stabilizes the config
format. We solve this problem, they'll throw us another curveball sooner
or later...