On 11/09/2012 06:56 AM, Alexander Bokovoy wrote:
The simple fact that you are feeding kickstart file to a single entity does not mean this entity cannot outsource actual tasks to others and run them later, be it post-install phase in the actual installer's session or after (a simulated) reboot. Input interface change is not needed for backend changes. If all you are interested is 'one go' installer from perspective of the feeding kickstart files, it would still be the same.
What anaconda is doing is taking that kickstart input and feed it into run-time tools in a way that those tools can do what we want them to do.
Except those tools change over time, and their inputs change over time, so anaconda breaks over time just in trying to take data in one place and feed it into another.
Isn't software fun? -- Jesse Keating Fedora -- Freedom² is a feature! -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
