On 01/12/2011 04:13 PM, Chris Lumens wrote:
The only reason I can think of is to impose order of execution
(setupData) of ks commands. I'd be afraid (as in all patches in this set
generally) of changing it even though it seems contrary to what we
do in stage 2 - requiring (and keeping to some extent) certain order
of commands in ks file, talking mainly with network command in mind.
Agreed on not touching it. I'm glad I'm not the only person confused by
this block.
For master, I'm working on an experimental set of patches that'll get
rid of this code entirely.
Nice, I'll remember to port my stuff on top of your patches
for master. I'm curious how the embedding will work out.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
