1 |
Really weel said Daniel. Thank you for being so open-minded. Just as an |
2 |
exemple, I'm a junior consultant and install some servers for company. |
3 |
I'm paid (a lot) day by day for this job. I can install a running server |
4 |
in 1 day because it takes some hours to compile an entire system. |
5 |
Managers won't understand that. BUT : I can install a binary gentoo |
6 |
(thanx to GRP for exemple), and provide some "tunning" stuff to the |
7 |
company later. that's make more sense, isn't it ? |
8 |
|
9 |
|
10 |
On Tue, 2003-09-16 at 08:44, Daniel Robbins wrote: |
11 |
> I should have posted this to gentoo-dev in the first place (was posted to |
12 |
> -core,) so here goes... |
13 |
> |
14 |
> On Mon, 2003-09-15 at 12:12, Sven Vermeulen wrote: |
15 |
> > Don't take this personally, but - just to make my mind clear - can't we |
16 |
> > (well, Gentoo that is) make a statement on what we want to achieve? |
17 |
> |
18 |
> I'll try to spell it out for you with a bit of Gentoo history. |
19 |
> |
20 |
> I created Gentoo because I couldn't find a Linux distribution that I |
21 |
> liked. The one predominant thing that I experienced with Linux |
22 |
> distributions is that the "distro tools" that managed the entire system |
23 |
> -- the tools that were supposed to make everything *easier* to use -- |
24 |
> really seemed to want a lot of attention and really got in the way of |
25 |
> what I wanted to do. I wanted to tell *them* what I wanted to do, but |
26 |
> they seemed more interested in telling *me* what *they* wanted me to do. |
27 |
> |
28 |
> So, I created Gentoo Linux, and designed Portage to be a more perfect |
29 |
> tool than what had existed before it. To do this, I made it very |
30 |
> flexible in allowing me to do what I wanted to do, and also tried to |
31 |
> make it flexible to allow others to do what I thought they might want to |
32 |
> do. |
33 |
> |
34 |
> If others wanted to see how a package got built, they could look at a |
35 |
> relatively easy-to-understand ebuild file and learn from it. If they |
36 |
> wanted to tweak how it got built, they took advantage of USE variables. |
37 |
> If they wanted to add a package, they created a new ebuild for the tree. |
38 |
> If they wanted to use a package, they simply emerged it and dependencies |
39 |
> were automatically resolved. |
40 |
> |
41 |
> People liked the Portage concept, and Gentoo Linux grew rapidly. We have |
42 |
> become known as a "from source" distribution, but the heart of the |
43 |
> Gentoo concept is not "from source." "From source" is an important and |
44 |
> key aspect of Gentoo, and something that was and will continue to be |
45 |
> necessary for Gentoo, but it is not the only issue or most fundamental |
46 |
> issue. The most fundamental issue is designing a technology that allows |
47 |
> us and others to do what they want to do, without restriction. |
48 |
> |
49 |
> To summarize the heart of Gentoo, imagine a user sitting in front of a |
50 |
> Linux system. What does he or she want do to? The Gentoo philosophy is |
51 |
> to allow this user to do what he or she wants to do, without getting in |
52 |
> the way. |
53 |
> |
54 |
> At around the time Gentoo was born, the thing that got in the way was |
55 |
> the lack of an easy way to build packages from source, to a user's |
56 |
> specifications. Currently, we've done that very well, but what we |
57 |
> haven't done very well is support pre-built packages, even though |
58 |
> Portage has supported building binary packages almost since its |
59 |
> inception. So we are doing that now. It's important that our tools |
60 |
> support binary packages, because binary packages are widely used and |
61 |
> widely in demand in the Linux community. If our tools don't support |
62 |
> binary packages, then we can't claim that our tools are designed to |
63 |
> allow a user to do anything he or she might want to do. If we purposely |
64 |
> choose to exclude binary support, then we are attempting to interfere |
65 |
> with how users might choose to approach particular problems, by instead |
66 |
> imposing our own will or view of how they should approach a problem. And |
67 |
> if we do not build binary packages, then we are not taking any steps to |
68 |
> ensure that our tools actually work well with binary packages, nor are |
69 |
> we taking steps to ensure that others can build binary packages, nor are |
70 |
> we able to *demonstrate* that our tools work well with binary packages. |
71 |
> Besides these philisophical reasons, there are many practical reasons to |
72 |
> create binary packages. |
73 |
> |
74 |
> The Gentoo philosophy, in a paragraph, is this. Every user has work they |
75 |
> need to do. The goal of Gentoo is to design tools and systems that allow |
76 |
> a user to do their work pleasantly and efficiently as possible, as |
77 |
> *they* see fit. Our tools should be a joy to use, and should help the |
78 |
> user to appreciate the richness of the Linux and free software |
79 |
> community, and the flexibility of free software. This is only possible |
80 |
> when the tool is designed to reflect and transmit the will of the user, |
81 |
> and leave the possibilities open as to the final form of the raw |
82 |
> materials (the source code.) If the tool forces the user to do things a |
83 |
> particular way, then the tool is working against, rather than for, the |
84 |
> user. We have all experienced situations where tools seem to be imposing |
85 |
> their respective wills on us. This is backwards, and contrary to the |
86 |
> Gentoo philosophy. |
87 |
> |
88 |
> Put another way, the Gentoo philosophy is to create better tools. When a |
89 |
> tool is doing its job perfectly, you might not even be very aware of its |
90 |
> presence, because it does not interfere and make its presence known, nor |
91 |
> does it force you to interact with it when you don't want it to. The |
92 |
> tool serves the user rather than the user serving the tool. |
93 |
> |
94 |
> The future goal of Gentoo is to continue to strive to create near-ideal |
95 |
> tools. Tools that can accomodate the needs of many different users (all |
96 |
> with divergent goals) with ease are extremely powerful. Don't you love |
97 |
> it when you find a tool that does exactly what you want to do? Doesn't |
98 |
> it feel great? Our mission is to give that sensation to as many people |
99 |
> as possible. |
100 |
> |
101 |
> It's fun to do this by creating a distribution from existing |
102 |
> freely-available code, like we are, because you can often give people |
103 |
> great satisfaction just by unlocking some of the coolness that has |
104 |
> already been created by someone else, just by making it more accessible. |
105 |
> Hope that helps, |
106 |
> |
107 |
> Daniel |
108 |
|
109 |
|
110 |
-- |
111 |
gentoo-dev@g.o mailing list |