Options for Booster and kernels?

[abenz1267]

Hi,

would it be within scope to add options to use booster instead of mkinitcpio and linux-zen over linux? Does that make sense? Also: what about intel/amd ucode?

Regards

[Torxed]

Ucode support has been in for a while and will come in the next release: #221
As for linux-zen and other kernels, has also been added about a month ago: #315

As for booster however, I'm not sure. mkinitcpio is what's officially used to build the ISO's (unless something's changed very recently) and I kinda like that it's pretty stable for what we're doing. I don't mind exploring the idea of using something else, or at least making us agnostic to whatever we want to use. It would more or less just be one more function or change the existing function:

archinstall/archinstall/lib/installer.py

Lines 294 to 300 in 7daaf11

	def mkinitcpio(self, *flags):
	with open(f'{self.target}/etc/mkinitcpio.conf', 'w') as mkinit:
	mkinit.write(f"MODULES=({' '.join(self.MODULES)})\n")
	mkinit.write(f"BINARIES=({' '.join(self.BINARIES)})\n")
	mkinit.write(f"FILES=({' '.join(self.FILES)})\n")
	mkinit.write(f"HOOKS=({' '.join(self.HOOKS)})\n")
	SysCommand(f'/usr/bin/arch-chroot {self.target} mkinitcpio {" ".join(flags)}')

But I feel that it's outside of the scope here and I don't know what risks/issues that might cause.

[Torxed]

I'll add to this, during development of #393 I figured one of the hooks might be able to do this. If you write a plugin, and load it (this would require a custom installation script) with a on_mkinitcpio() hook that returns anything (for instance just a return True) - you could interrupt the use of mkinitcpio and call whatever you like.

This is not as smooth and easy as the guided installer, but this would allow you to do this very thing.
Assuming that PR gets included.