--- design.xml.old 2004-09-17 10:55:57.405814976 -0400
+++ design.xml 2004-09-17 10:48:00.454322624 -0400
@@ -2,7 +2,7 @@
-
+
Gentoo Linux Installer
@@ -12,19 +12,20 @@
Nicholas D. Wolfwood
-
-
An introduction to the Gentoo Linux Installer project discussing it's purpose,
design structure, and participants.
+
+
1.0
Jan 29, 2004
Overview
+Overview
@@ -53,6 +54,7 @@
Features
+Features
@@ -65,6 +67,7 @@
+
Multiple front ends
@@ -80,6 +83,7 @@
+
Reusable back end framework
@@ -94,6 +98,7 @@
+
Automated deployment
@@ -109,6 +114,7 @@
+
Dry run profile generation
@@ -122,6 +128,7 @@
+
Full support for all Gentoo architectures
@@ -136,6 +143,7 @@
+
Specialized profiles
@@ -149,6 +157,7 @@
+
Open policies and standards use
@@ -162,6 +171,7 @@
+
Integration with future configuration projects
@@ -180,6 +190,7 @@
Design and Structure
+Design and Structure
@@ -190,13 +201,14 @@
A few design requirements were stated:
+
+
- Multiple UIs must be supported (abstracted view support)
- A complete separation of model, view, and control logic be kept
- All features must be supported regardless of front end or architecture
- Automated deployment always be possible
-
To this end, the installer platform (as the entire system is referenced) is
@@ -205,6 +217,7 @@
+
Front end (Client)
@@ -236,6 +249,7 @@
+
Back end (API or framework)
@@ -253,6 +267,7 @@
Since the framework is segregated from the client, it may be used for customized
installation products developed by users. The major classes are as follows:
+
-
A controller class that dictates, based on the architecture template (an XML
@@ -266,7 +281,6 @@
deployment server for later use.
-
Other minor classes may be used for intermediary support, but these two solidify
@@ -275,6 +289,7 @@
+
Deployment server
@@ -312,6 +327,7 @@
Process
+Process
@@ -335,6 +351,7 @@
Contact
+Contact
@@ -353,6 +370,7 @@
Authors and Contributors
+Authors and Contributors