| 1 |
Like linuxconf on redhat... oh no. |
| 2 |
|
| 3 |
I like this way to have one engine and some toolkits but its much work |
| 4 |
to optimize all of them at the same. It's better to have one working |
| 5 |
native qt-version like many versions which don't work really well. |
| 6 |
|
| 7 |
Another great idea is to store first all informations and then do the |
| 8 |
setup. I personally don't like all these setup's like mandrake, suse and |
| 9 |
Windows which ask me all ten minutes some question. I want to do all |
| 10 |
first and then only press 'do it so'. So you could build preconfigured |
| 11 |
CD's which autoinstalls on a new system. Insert CD -> Boot -> Auto |
| 12 |
Install -> Reboot -> Complete working setup. |
| 13 |
|
| 14 |
Thanks in advance |
| 15 |
|
| 16 |
Sebastian |
| 17 |
|
| 18 |
|
| 19 |
-----Ursprüngliche Nachricht----- |
| 20 |
Von: gentoo-dev-admin@g.o [mailto:gentoo-dev-admin@g.o] Im |
| 21 |
Auftrag von Mikael Hallendal |
| 22 |
Gesendet: Montag, 7. Januar 2002 03:07 |
| 23 |
An: gentoo-dev@g.o |
| 24 |
Betreff: Re: [gentoo-dev] GUi installer brainstorm |
| 25 |
|
| 26 |
mån 2002-01-07 klockan 02.10 skrev Geert Bevin: |
| 27 |
> I've been thinking about the core engine, and what would be nice is an |
| 28 |
> abstracted installer storyboard language. This might for example use |
| 29 |
xml |
| 30 |
> to define actions, sequences, paths, default responses, etc etc |
| 31 |
|
| 32 |
This sounds exactly like what I was thinking :) |
| 33 |
That way it's going to be easy to define commands and stuff that can be |
| 34 |
used to auto-insert on the command prompt if the user wants that. |
| 35 |
|
| 36 |
Regards, |
| 37 |
Mikael Hallendal |
| 38 |
|
| 39 |
-- |
| 40 |
Mikael Hallendal |
| 41 |
Gentoo Linux Developer, Desktop Team Leader |
| 42 |
CodeFactory AB, Stockholm, Sweden |
Archives