Re: Do the per-profile and per-system snippets override the "default" snippet?
Michael DeHaan schrieb:
Rainer Duffner wrote:
> Hi,
>
> the per-profile and per-system snippet stuff is cool - but it seems the
> custom snippet overrides the default one.
> While I can see that this is something people may also want, it's not
> what I need.
> The per-profile or per-system snippets I want are in 99% of the cases
> additions to what the "standard" snippet delivers.
>
>
> Can this be implemented?
>
>
>
Yes, you can do this now: use two snippets right next to each other:
SNIPPET::blarg
SNIPPET::blarg_aux
For the default case, blarg_aux is a BLANK snippet.
And just override blarg_aux as needed.
OK, I think I don't "get" it ;-)
When I write:
%post
SNIPPET::services_common
SNIPPET::services_common_aux
I get a
%post
/sbin/chkconfig postfix off
# Error: no snippet data
At the relevant position in the rendered kickstart file.
The first part is the per_profile snippet.
I use the dev-version of cobbler from yesterday.