> In general, I don't like to make multiple instances of a
kickstart
> command into errors. This is so that kickstart files can make use of a
> %include to do some primitive form of inheritance - a site can use some
> generic base kickstart file, and then override directives later in more
> specific %includes.
Good point. What do you suggest we do about this bug then?
I'd like to know why anaconda does a traceback in this situation. It
seems pretty odd to me. One potential fix in pykickstart that I think I
would be happy with would be having later calls to the clearpart command
first clear out the data object before parsing. That preserves the
inheritance idea (kinda, sorta) while hopefully also fixing up whatever
anaconda's mad about.
- Chris