Join GitHub today
Consistent Home Limit Check #301
yast-storage-old checked the limit when to propose a separate home partition differently between
In one case, it took the other partitions that needed to be created into account (swap, /boot, /efi-boot), in the other it didn't. This is inconsistent.
Make the proposal
Take the swap partition into account and just ignore the boot partition(s). This is what this PR does.
While it would be nice to be exact, the code adding a boot partition is all over the place in StorageProposal.rb and its 117 functions in its 6722 lines of code. That old code can only handle one single boot partition; it's either
Anyway, since a boot partition is only a few MiB anyway, this doesn't change the overall calculation that much; this is about the same order of magnitude than overhead due to LVM management which in the other case would also cause a slight difference. I think we can live with that.
Trying not to overengineer this.