<p><br>
On Mar 29, 2012 8:00 AM, "Paul Howarth" <<a href="mailto:paul@city-fan.org">paul@city-fan.org</a>> wrote:<br>
><br>
> On Wed, 28 Mar 2012 22:16:25 +0200<br>
> Reindl Harald <<a href="mailto:h.reindl@thelounge.net">h.reindl@thelounge.net</a>> wrote:<br>
> > maybe the tone was minimal rude because i do absolutely<br>
> > not understand why anyone can have the idea "hey let us<br>
> > remove the whole custom partitioning and replace with<br>
> > kickstart only" to solve problems with it<br>
><br>
> That's not what I understood from Adam's description, which was:<br>
><br>
> > It's worth bearing in mind there's a giant anaconda UI rewrite still<br>
> > pending, which entirely redesigns the storage configuration GUI. One<br>
> > of the other major changes is that it makes all installations<br>
> > kickstart-driven. The GUI will just produce a kickstart file, which<br>
> > anaconda will then process to perform the actual install.<br>
><br>
> Now my understanding of that doesn't include anything about removing<br>
> custom partitioning. It's all about splitting up the functionality of<br>
> anaconda into two distinct parts - the GUI configuration part, which I<br>
> would expect still to contain custom partitioning, and a back-end that<br>
> implements the configuration, where the configuration is passed to it<br>
> in the form of a kickstart file (either the output of the GUI part, or<br>
> a kickstart file prepared earlier by the user).<br>
><br>
> My understanding is based entirely on Adam's description since I'm not<br>
> involved in anaconda development, but it strikes me as being a good<br>
> thing as it would split one large process into two, presumably smaller<br>
> ones, which would help solve the problem of running anaconda on<br>
> machines with less memory.</p>
<p>That's my understanding as well so it's not removing functionality but rather the underlying mechanism and implementation of them. This is good because it will allow a consistent outcome whether using the GUI, a kickstart file or something else like media and appliance creator and likely considerable simplification of the code too.</p>
<p>Peter<br></p>
<p>> --<br>
> devel mailing list<br>
> <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/devel">https://admin.fedoraproject.org/mailman/listinfo/devel</a></p>