1 |
Trenton Adams schreef: |
2 |
> Oops, forgot to reply to everything. |
3 |
> |
4 |
> On 1/6/06, Holly Bostick <motub@××××××.nl> wrote: |
5 |
> |
6 |
>> Trenton Adams schreef: |
7 |
>> |
8 |
>>> On 1/5/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
9 |
>>> |
10 |
>>> |
11 |
>>>> On Thu, 5 Jan 2006 16:32:20 -0700, Trenton Adams wrote: |
12 |
>>>> |
13 |
>>>> |
14 |
>>>> |
15 |
>>>>>> something like |
16 |
>>>>>> |
17 |
>>>>>> if_blocked_by('openmotif') ewarn "You must unmerge |
18 |
>>>>>> openmotif before proceeding" |
19 |
>>>>> |
20 |
>>>>> Yes, or as follows... |
21 |
>>>>> |
22 |
>>>>> if_blocked_by('openmotif') auto_unmerge('openmotif') # |
23 |
>>>>> continue with merge which should automatically be merging |
24 |
>>>>> openmotif anyhow. |
25 |
>>>> |
26 |
>>>> Absolutely not! I don't want portage removing something I may |
27 |
>>>> be using at the time without my saying so. |
28 |
>>> |
29 |
>>> |
30 |
>>> Good point. Perhaps it should ask then? |
31 |
>>> |
32 |
>>> |
33 |
>> |
34 |
>> Well, it does, by stopping and waiting for you to perform an action |
35 |
>> and either restart the stopped process (if the action you took was |
36 |
>> to unmerge the blocking package), or to forego the stopped process |
37 |
>> entirely, if you choose not to remove the blocked package because |
38 |
>> you want to keep it for whatever reason (it could happen). |
39 |
>> |
40 |
>> You're assuming that unmerging the blocking package is *always* the |
41 |
>> right solution for everyone at all times (in this case, it's not |
42 |
>> really relevant, since motif-config will itself re-install |
43 |
>> openmotif), but the point of Gentoo is that you are in control. If |
44 |
>> I am in control, then I have to decide what I want done in each |
45 |
>> particular situation that occurs, which is exactly what I have to |
46 |
>> do with the current setup-- very obviously, since Portage will stop |
47 |
>> until I make a decision and act on it. So fine, your new updated |
48 |
>> Portage informs me there's a block, and says, "I could do this to |
49 |
>> solve it, shall I?" I myself am going to say "no", because I want |
50 |
>> to know the nature of the block, and how Portage's proposed action |
51 |
>> is going to affect the system that I have carefully customized to |
52 |
>> my individual needs. |
53 |
> |
54 |
> |
55 |
> Yes, flexibility is GREAT. That's one reason I really like gentoo, |
56 |
> and linux in general. However, I also like simplicity, or should I |
57 |
> say, I like to have the choice. So, one could easily make gentoo |
58 |
> have auto-detect and handle features, while allowing configuration |
59 |
> changes that disable automatic behaviour. You could have individual |
60 |
> enable/disable options for each feature, as well as one global |
61 |
> feature than enables/disables all auto-detect features. Then you |
62 |
> could have include/excludes for each feature so that the global would |
63 |
> not override them. |
64 |
> |
65 |
> So, the bottom line is this, one person says that things are |
66 |
> difficult because they need to be, in order to be flexible. But I |
67 |
> say that if things are truly flexible, then it should also be |
68 |
> possible to make them automatic, or simple. That's what I call |
69 |
> ULTIMATE flexiblity, which is what I mentioned in another post that I |
70 |
> made. When I originally started with gentoo linux, I read the part |
71 |
> about why gentoo linux came about. Basically it was all about doing |
72 |
> things the way you want. Well, I like the flexiblity, but I also |
73 |
> want the simplicity. :) Let us have the simplicity of RedHat, and |
74 |
> RPMs (waiting for flames), but with flexibility as well. |
75 |
|
76 |
Well, if this is your opinion, I must then accept the burden of being |
77 |
one of those members of the Linux community you mention |
78 |
|
79 |
Trenton Adams schreef: |
80 |
|
81 |
> Yes, and I've noticed there's a big problem with the linux community |
82 |
> at large. People that know and understand linux have a lot of the |
83 |
> times not helped the "open source" intiative, in that they like |
84 |
> things to be difficult, |
85 |
|
86 |
Although this is not strictly true.... I don't *like* things to be |
87 |
difficult, /per se/ but I do tend to do things "the hard way" rather |
88 |
than "the easy way" |
89 |
|
90 |
> because it makes them somehow seem smarter. In all reality, it |
91 |
> doesn't take a genius to use linux, just someone who likes to read a |
92 |
> whole lot. |
93 |
|
94 |
I do like to read a whole lot (always have), and I don't so much care |
95 |
how smart anyone thinks I am, but if I am in any way smart, I do want |
96 |
that to be recognized, which is a different thing. |
97 |
|
98 |
But if you leave out the rather insulting insinuation that such users |
99 |
are not in fact smart, but ego-trippers who just have nothing to do but |
100 |
read dry technical texts that no "normal" person would ever bother with, |
101 |
I'll cop to the charge. |
102 |
|
103 |
The thing is, I prefer things to be slightly more difficult because I |
104 |
believe that people using advanced tools should have a clue about how |
105 |
they work and how to use them properly. |
106 |
|
107 |
As I have said before, and will likely say again in the future, I |
108 |
believe that a policy of providing advanced technology, dumbed-down so |
109 |
that it "Just Works" to the "unwashed masses" (let us say, my |
110 |
boyfriend's grandmother, who is a very nice lady, or my aunt, or his |
111 |
mother, who are of an age and about the same level of computer expertise |
112 |
and interest-- which is to say, "none", although my bf's mother has now |
113 |
had a computer forced on her), is dangerously unwise. |
114 |
|
115 |
We have seen the results of doing so in both large and small ways, yet |
116 |
we persist. I believe that advanced technology should be sufficiently |
117 |
difficult to use until such time as it is "safe" (if it ever is) that |
118 |
people who don't want to think at all won't use it, to be frank. Because |
119 |
I don't want someone who doesn't want to think to be in control of |
120 |
advanced technology or tools whose misuse may well impact me (these are |
121 |
"advanced tools", after all, and that is one of the qualities that makes |
122 |
them "advanced"-- a wide range of impact), even if I never know that |
123 |
person, and never will. |
124 |
|
125 |
At least I know me, and at least if I rain destruction on my PC and my |
126 |
network, it's my own fault. I'm willing to take responsibility for that. |
127 |
I'm not willing to trust faceless developers at RedHat (or SuSE/Novell, |
128 |
or even Mandriva) with these responsibilities. On the other hand, I am |
129 |
willing to trust the Gentoo devs to a much greater degree, because 1) |
130 |
they *share* their knowledge freely (so I know what they're doing, if I |
131 |
can understand it); 2) they welcome my contribution/participation in |
132 |
what they are doing, in fact recommend it; and most importantly, 3) they |
133 |
draw and respect boundaries, beyond which I am expected to take |
134 |
responsibility for myself... which is how a good parent/administrator |
135 |
trains children/"average users" to become competent and knowledgeable |
136 |
adults/users. |
137 |
|
138 |
Something I've always remembered is that when I was learning to drive, |
139 |
the Department of Motor Vehicles required that all proposed licensees |
140 |
had to take this class where we watched a film about the evils of |
141 |
drinking and driving I think it was. In any case, the instructor said, |
142 |
"Most people on the road are not /drivers/. They are /operators of |
143 |
vehicles/." The difference being that operators of vehicles can get the |
144 |
vehicle from Point A to Point B, but don't really understand much about |
145 |
the complex interaction between the advanced technological tool they are |
146 |
operating (which they likely also know little about), the environment |
147 |
they are operating in, where other advanced technological tools are also |
148 |
operating, the impact of their operation on the (possibly incompetent) |
149 |
opertation of the others in the environment, and how the environment |
150 |
itself has been shaped specifically to make managing the interaction of |
151 |
all these elements and various random, unpredictable variables as smooth |
152 |
as possible, so that the goal can be reached-- all of which a driver |
153 |
would/must have a greater sense of. He proposed to set us on the path to |
154 |
being drivers, rather than operators of vehicles. |
155 |
|
156 |
Gentoo has a similar philosophy in the computer field. I can get your |
157 |
point about "ULTIMATE flexibility", but in the real world, in many |
158 |
fields, you are supposed to learn the hard way (learn the rules first) |
159 |
before you may take the easy way (break the rules), if you then choose |
160 |
to do so. And we all know that "most people", offered the choice of an |
161 |
easy way and a hard way are going to take the easy way *all the time*, |
162 |
and thus flail around in relative ignorance for the rest of their days. |
163 |
|
164 |
Which is exactly what I'm against-- ignorance. No, I don't want Gentoo |
165 |
to be all that "easy". But not because I want to put myself up as better |
166 |
than anybody-- I'm not in fact better than anybody. $DEITY knows, Neil |
167 |
knows way more than me, and even he makes mistakes :-) . But you can't |
168 |
learn if you don't try, and you can't try if you don't get the chance |
169 |
(because everything is so "easy" that you never have the opportunity). |
170 |
|
171 |
And I want to learn. I don't want to be ignorant. And I don't want |
172 |
Gentoo to "do it for me" until I know enough to know what letting it do |
173 |
so means-- at which point letting it do it for me is completely |
174 |
irrelevant (though possibly convienient in some situations), since by |
175 |
that time I know enough that what it's going to automatically could be |
176 |
done manually by me in the same amount of or possibly less time. |
177 |
|
178 |
So I am of the opinion that, as I said before, this is a cosmetic issue. |
179 |
If the devs have time to code a tool that will give more comprehensive |
180 |
output about the nature of any given block, and propose solutions that I |
181 |
can choose to accept or not, that's all very nice, as I said. |
182 |
|
183 |
But the X amount of time that it takes them to do that is about the same |
184 |
X amount of time that it takes me to just look the information up myself |
185 |
(the time it takes me to decide is unchanged, since I have to do that |
186 |
either way), and frankly, I'd rather that the devs spent that X amount |
187 |
of time doing something more substantive to enhancing my Gentoo experience. |
188 |
|
189 |
Maybe it's just me. |
190 |
|
191 |
Holly |
192 |
-- |
193 |
gentoo-user@g.o mailing list |