Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-installer
Navigation:
Lists: gentoo-installer: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-installer@g.o
From: Paul de Vrieze <pauldv@g.o>
Subject: Re: a few different questions
Date: Tue, 3 Feb 2004 11:22:39 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 03 February 2004 05:13, Eric Sammer wrote:
>
> Aha. I see now. No, all action is delayed until all decision making is
> complete. This is for two reasons (one intended, one a nice side
> effect): 1. The front end is acting as just a special kind of install
> profile editor of sorts so teh backend is really the automated
> deployment part with some of the features missing. This makes for very
> good reuse of design / code. 2. Users like to experiment and a "Back"
> button is a nice comfort to newer users. Blowing away their partition
> table prior to all decisions being made might upset some folks.

One could offer an option to force the actions to be done. It would be 
needed when users perform manual actions (but not in all cases). Of 
course forcing actions will disable the back button so probably warrants 
a warning.

>
> > Just the same as most installers work, instead of how the GLIS
> > frontend and backend works.
>
> Actually, as far as I know, most installers delay destructive actions
> even if they *say* they don't. Of course, I haven't looked at the code
> for any of these products recently, but it seems logical that if you
> performed a destructive operation such as altering a partition table
> *and* you provided a back button... well, I just don't know how you'd
> make that work in a reasonable, predictable, and safe fashion.
>
> > With the frontend that Scott Hadfield and I jointly
> > wrote for GLIS, the frontend creates the config file which gets
> > passed to the backend when the config is done. That is not
> > real-time.
>
> Right. This will function in a similar manner. I think this is a
> better design than firing off each part piecemeal.

It is the task of the frontend to either save up the actions or to send 
them to the backend immediately. As long as the backend can perform 
actions as soon as they are received (incomplete xml file) the backend 
can handle whatever you want.

Paul

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAH3ZvbKx5DBjWFdsRAoWcAJ4xW6dh9D4w6in+flp0ws5nPkg5QwCgtQaS
DZopM4VszYS5hGYQiKX4acQ=
=Dn/z
-----END PGP SIGNATURE-----

--
gentoo-installer@g.o mailing list

Replies:
Re: a few different questions
-- Eric Sammer
References:
a few different questions
-- Andrew Gaffney
Re: a few different questions
-- Andrew Gaffney
Re: a few different questions
-- Eric Sammer
Navigation:
Lists: gentoo-installer: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: a few different questions
Next by thread:
Re: a few different questions
Previous by date:
Re: New class diagram and use case
Next by date:
Re: New class diagram and use case


Updated Jun 17, 2009

Summary: Archive of the gentoo-installer mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.