| 1 |
On Tuesday 03 February 2004 21:36, Nicholas D. Wolfwood wrote: |
| 2 |
> On Tue, 2004-02-03 at 12:09, Nathaniel McCallum wrote: |
| 3 |
> > The backend doesn't actually do anything until all options have been |
| 4 |
> > chosen. ALL installation activity waits until AFTER the user would |
| 5 |
> > click "finish" (just an example). Nothing should be done until the user |
| 6 |
> > has made all choices. Once the user has made all choices, it will pass |
| 7 |
> > the xml file to the backend and perform the whole installation. This is |
| 8 |
> > really the desireable operation. |
| 9 |
> |
| 10 |
> And as esammer already pointed out, this allows for reuse of the backend |
| 11 |
> in both attended and unattended installs. So, the interactivity is in |
| 12 |
> the frontend, the backend's responsibility is to perform an install |
| 13 |
> based on an install profile (what to do), and an arch profile (how to do |
| 14 |
> it), the frontend just gets an install profile together for the backend |
| 15 |
> to use, and optionally gathers status information from the backend as it |
| 16 |
> performs the install. |
| 17 |
|
| 18 |
All I ask is for the backend to have a mode designed in that would allow the |
| 19 |
feeding of the install profile incrementally. That would mean that one could |
| 20 |
feed the backend an incomplete install profile and it would do what it could |
| 21 |
based on that. Also take into account that this install profile will not |
| 22 |
necessarilly contain all stages. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives