Subject: Re: Graphical Sysinst in 2.0
To: Timo Sch?ler <firstname.lastname@example.org>
From: Bill Studenmund <email@example.com>
Date: 09/07/2004 09:40:42
Content-Type: text/plain; charset=us-ascii
On Sun, Sep 05, 2004 at 12:42:18PM +0200, Timo Sch?ler wrote:
> >The current sysinst code is tightly coupled with the curses code which=
> >want to change. Also, I'm working on better error checking and things
> >like that too.
> that sounds cool :)
> why not taking this chance of writing (perhaps) a new sysinstall to=20
> make further changes?
> * using XML for data sets like the timezone list (there's more or less=20
> a kind of dynamic change in it)
I'm not sure if this step is needed. While I actually like XML for a=20
number of things, I don't think it's needed here. I see XML as the right=20
choice if you have a lot of tools (or even just two) that need to parse a=
file, but only need to understand some of it. With XML's structure, the=20
parsers can ignore the parts they don't understand yet still be confident=
they are correctly-reading the file.
Time zone info isn't kept in XML files, so the only consumer of such a=20
file would be the installer. Since only one tool (or one library) will=20
read the file, XML doesn't gain us much.
> * making the whole process (more?) scriptable, e.g. for mass rollout=20
> events (might be very useful in cluster environments)
I thought this feature'd already been added to sysinst? Maybe I'm=20
An installer that is set up to use multiple UIs could easily have a script=
UI that just reads a task script. Add that to a tool that will take the=20
log for an install and make such a script, and we easily have a scripted=20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----