Before I left for the EFI testing days last week, I was working on
moving all anaconda configuration information into ksdata objects. The
most obvious reason for that is to reduce the number of places we have
config data, but other reasons came up too. First, we could largely get
rid of the writeKS methods scattered throughout anaconda and just use
pykickstart. Second, our new UI design involves the UI writing out a
kickstart file and the backend reading it in. So it's well-suited to
this kind of change. Third, always doing an install as a kickstart
install means the defaults can be stored centrally in a kickstart file
and always read in.
With that in mind, I've done a rough draft of moving a couple very easy
pieces around. The easy pieces are hard, the hard pieces are very hard.
I'm hoping things get easier as I untangle everything. I'm posting this
now so people can get a sense for what I'm doing and tell me if I'm on
the right track or not - before I tackle the hard stuff. Patches are
here:
http://clumens.fedorapeople.org/ksdata/
- Chris
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
