1 |
First off all, the install process is only a portion of making gentoo |
2 |
*easier*. At it is kind of a tangent to the original discussion. |
3 |
But, none the less, it is a good discussion. |
4 |
|
5 |
On 1/7/06, Holly Bostick <motub@××××××.nl> wrote: |
6 |
> Trenton Adams schreef: |
7 |
> > Interesting points, but |
8 |
> > |
9 |
> > On 1/7/06, Abhay Kedia <abhay.ilugd@×××××.com> wrote: |
10 |
> > |
11 |
> >> On Saturday 07 January 2006 22:00, Trenton Adams wrote: |
12 |
> >> |
13 |
> >>> I like both that my car just works, and I don't have to know how |
14 |
> >>> the pistons go up and down, but that I can also look under the |
15 |
> >>> hood if I so desire. |
16 |
> >>> |
17 |
> >> |
18 |
> >> Thinking on the wrong lines again and what you want can never |
19 |
> >> happen, at least with Gentoo; because Gentoo does not give you a |
20 |
> >> working car at all. It just gives you spare parts (ebuilds & |
21 |
> >> packages), books to read (documentation) and a tool box (portage). |
22 |
> >> Then it tells you to go ahead and make your own car. It totally |
23 |
> >> depends on you whether you want to make it a blazing fast Ferrari |
24 |
> >> or a classy Limo. To achieve anything of that sorts you *HAVE TO* |
25 |
> >> know how the pistons go up and down. If you don't read and just put |
26 |
> >> together the pieces in a random order then you might make a moving |
27 |
> >> car but it will not be a working one. Moral of the story? To have |
28 |
> >> full control, you gotta know how things work inside the engine :) |
29 |
> > |
30 |
> > |
31 |
> > Well actually, it could happen. If I had a menu of packages to be |
32 |
> > installed during some sort of automated install process, then I'm |
33 |
> > still customizing my system the way I want. So once again, you |
34 |
> > absolutely *CAN* have gentoo flexibility with easy of install |
35 |
> |
36 |
> Just a quick question: |
37 |
> |
38 |
> Isn't creating "a menu of packages to be installed" part of the install |
39 |
> process? |
40 |
> |
41 |
> If not, because you did not create this menu yourself, then you are not |
42 |
> "customizing your system the way you want", but rather choosing the most |
43 |
> suitable for you amongst a list of pre-defined-- thus, by definition, |
44 |
> limiting-- options. |
45 |
|
46 |
Here we go again, who says that you have to limit it to a menu? Give |
47 |
a menu, but allow a graphical shell during install for those that want |
48 |
to do extra packages, or whatever. Or, even provide a dynamically |
49 |
extendable menu that can grab packages lists from other places, from |
50 |
another CD, floppy, Internet, etc. So, to not provide a menu would be |
51 |
*limiting* as well. But I do agree with you Holly, that providing |
52 |
*only* a *predefined* graphical menu for package installation would be |
53 |
limiting. |
54 |
|
55 |
Now, I'm just brain storming here... |
56 |
|
57 |
Wouldn't it be beneficial to provide automated graphical installs for |
58 |
gentoo, but provide the option to open a graphical shell at *all* |
59 |
stages of the installation process? Wouldn't that be ultimate |
60 |
flexibility? I read about the new graphical install for gentoo, and |
61 |
perhaps it already does this!?!? |
62 |
|
63 |
> |
64 |
> If you did create the menu of packages yourself, and it then is (as it |
65 |
> must be) considered part of the installation process, then isn't the |
66 |
> installation process no longer "easy", by your definition of "easy"? |
67 |
|
68 |
Well, this is a side tangent, given my reply just above. None the |
69 |
less, all of *my* installs from the point after I created my *own* |
70 |
menu would be easy. |
71 |
|
72 |
> |
73 |
> Not quite following the logic here. |
74 |
> |
75 |
> Holly |
76 |
> -- |
77 |
> gentoo-user@g.o mailing list |
78 |
> |
79 |
> |
80 |
|
81 |
-- |
82 |
gentoo-user@g.o mailing list |