https://bugzilla.redhat.com/show_bug.cgi?id=1576413 --- Comment #13 from Bryn M. Reeves <bmr@xxxxxxxxxx> --- > If Boom cannot handle this, then it needs to do something to make that work. I don't think that it's reasonable to expect boom to make things work that are explicitly outside the scope of the standard (BLS) that we are following. We can try to find ways to accommodate it to the best extent possible, and will look at doing so, but fundamentally we will always be limited by the applicability of the standard that we are adopting. > My understanding is that boom doesn't do any _real_ boot management functions, > and instead just generates configuration for loaders like GRUB2, rEFInd, or sd- > boot to use instead. Define "real boot management" ;-) The purpose of this is as documented: to allow *any* booted instance of the OS (including snapshots, which may have been taken prior to the creation of other managed instances) to manage *any other*. This can only be done if there is a single, shared system-wide source for this configuration (which is exactly what the BLS sets out to create). -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
