1 |
On 01/02/2012 10:05 AM, Alan McKinnon wrote: |
2 |
> |
3 |
> So when the user tells portage to emerge (not merge) something it goes |
4 |
> in world as obviously that's what the user wanted. Presumably the user |
5 |
> knows what they are doing and can deal with both pieces. If the user |
6 |
> would rather have software hold his hand, that user is better served by |
7 |
> Windows or Ubuntu or any number of user-centric distros, but probably |
8 |
> not by Gentoo. |
9 |
> |
10 |
> This isn't elitist, it's just the way things are. Portage's job is to |
11 |
> listen to *you*, not to to tell you what you want. The automation |
12 |
> portage provides is just the logical conclusion of what should happen |
13 |
> in future after you emerged something. |
14 |
> |
15 |
|
16 |
That unspoken agreement is only beneficial if I have the means by which |
17 |
to tell portage what I want it to do. The problem lies at a higher |
18 |
level: I think I'm telling portage to update a package, but that's not |
19 |
what --update means. It's hard for me to tell portage what I want it to |
20 |
do, so the fact that it assumes I know what I'm doing isn't constructive. |
21 |
|
22 |
I wouldn't call it elitist or blame anyone for the change; the entire |
23 |
premise for my argument is that people make mistakes. But I do think |
24 |
it's bad engineering: 50% of users are going to think it works the wrong |
25 |
way no matter which one you choose, but only one of them screws up your |
26 |
system when you get it wrong. |