Gentoo Archives: gentoo-installer

From: "Nicholas D. Wolfwood" <wolfwood@××××××××××××××××××.com>
To: gentoo-installer@l.g.o
Subject: Re: [gentoo-installer] New class diagram and use case
Date: Tue, 03 Feb 2004 20:36:59
On Tue, 2004-02-03 at 12:09, Nathaniel McCallum wrote:
> The backend doesn't actually do anything until all options have been > chosen. ALL installation activity waits until AFTER the user would > click "finish" (just an example). Nothing should be done until the user > has made all choices. Once the user has made all choices, it will pass > the xml file to the backend and perform the whole installation. This is > really the desireable operation.
And as esammer already pointed out, this allows for reuse of the backend in both attended and unattended installs. So, the interactivity is in the frontend, the backend's responsibility is to perform an install based on an install profile (what to do), and an arch profile (how to do it), the frontend just gets an install profile together for the backend to use, and optionally gathers status information from the backend as it performs the install. -- Nicholas D. Wolfwood <wolfwood@×××××××××××××××××.net> -- gentoo-installer@g.o mailing list


Subject Author
Re: [gentoo-installer] New class diagram and use case Paul de Vrieze <pauldv@g.o>