On 03/27/2013 03:20 PM, Chris Lumens wrote:
> 3) This patch implements the feature Stef asked for his realmd
addon
> - he was affraid that customers will regard %addon section in kickstart
> as something that is not really supported that well
> - so he asked us to look into allowing the addons to define their own
> "first class" kickstart command that will not be distinguishable from
> the rest
> - I see two issues with it. One is validation, and the second is that
> when addon is missing, sections are gracefully saved and transfered to
> the output kickstart without breaking anaconda. Unknown command raises
> an exception.
> - Regarding validation.. the whole kickstart addon implementation should
> be moved to pykickstart so the validation tools can load the addons as
> well.
This is my primary concern. So instead of looking like second class
support (which I don't believe at all - this feels entirely too much
like "we've got to do something now!" scare tactics), it will look like
first class support but in reality be second class support behind the
scenes. You won't be able to use the %addon-containing kickstart file
with anything that uses pykickstart and get what you expect. I don't
see how that's better.
So do you think we should put the realmd integration directly in
anaconda, rather than trying to implement it as an addon using the
incomplete addon code?
I think this is going to have to move to pykickstart before any
final
release goes out.
Right. So how much work is this? Do you think it's realistic to do
before Fedora 19?
Cheers,
Stef