When I re-read the kickstart default template, I realised that the line (template_name + “custom_packages”) isn’t just create custom_packages snippet it’s the template name AND custom_packages as the snippet name.
(I’m still not sure that’s correct).
If that’s true that means I’d have a snippet called “Kickstart Default custom_packages”
that doesn’t feel right for a snippet name with white spaces like that ? which makes me think I’ve not understood how to use this snippet.
Could someone explain how this is supposed to work please ?
(side question, how is this snippet getting included, I thought all snippets had to be prefixed with a @)
I never used this snippet, but I am pretty sure you understood correctly how it works, the snippet should be called “Kickstart Default custom_packages”. This is probably inteded as a way to make customizing your installation easier, while looking through “Kickstart Default” I realized there were several of these imports, for different sections of the installer.
The “usual”/old way of customizing your installation was to clone the default templates and customize those or write your own templates from scratch. This approach needs more maintenance, though, since you have to update and maintain your the templates yourself.
The template is included via the makro/function “snippet_if_exists”, which checks if a snippet by that name exists and includes it if it does. I am not sure where you got the idea from that snippets need to be prefixed with @, I cannot remember I ever saw that notation. The template writing documentation says you normally import snippets via the “snippet” function.
new-no-dns-base-kickstart - assigned it CentOS 8 and Rock9
created a custom snippet called “new-no-dns-base-kickstart custom_packages” (I’m really uncomfortable witih the snippet having a space in the name
snippet looks like this (the bold is actually a quote prefixed with # - the formatting is treatin # as bold)
If there is really no space in "custom_packages" then the full name does not contain a space, i.e. it would be "new-no-dns-base-kickstartcustom_packages" and not "new-no-dns-base-kickstart custom_packages"
I see that, and I’ve shamefully mixed my work around with the official view - to try to work with this I cloned the “kickstart default” package so that I could play with it to get it working, hence the name change.
(which your pointer has allowed me to fix)
the actual Kickstart Default code block looks like this
