Repackage lorax templates?

[Brian C. Lane]

I think this was something Will and I had discussed at one point:

Split the share/*tmpl file and the bootloader configs out into a
separate package like lorax-generic-templates. This would make it
clearer (along with some docs) that lorax can be used to create
customized boot isos. eg. include or exclude specific addons, dependent
packages, custom boot menus, etc.

This would fit in with making a docker kickstart addon package that some
variants would only be included in some variants, or modular payload
support, etc.

[Chris Lumens]

Post by Brian C. Lane
Split the share/*tmpl file and the bootloader configs out into a
separate package like lorax-generic-templates. This would make it
clearer (along with some docs) that lorax can be used to create
customized boot isos. eg. include or exclude specific addons, dependent
packages, custom boot menus, etc.
This would fit in with making a docker kickstart addon package that some
variants would only be included in some variants, or modular payload
support, etc.

Sure, I think this is a reasonable thing to do as long as it's a small
number of packages. As a distribution, I think we break things up into
entirely too many and too small chunks.

- Chris