1 |
Am 12.03.2013 08:33, schrieb Yuri K. Shatroff: |
2 |
> |
3 |
> Again, following your logic, why not just let the user himself |
4 |
> ./configure && make && make install as in old days? What is portage for? |
5 |
|
6 |
Following your logic, if there's even one tool to make life easier |
7 |
everything has to be absolutely easy. So we should now utilize fancy |
8 |
wizards? Once again, that's following your logic. |
9 |
|
10 |
> |
11 |
> That is a testing issue. Of course, one can never know what will |
12 |
> change, or whether the code contains a bug (before one is detected), |
13 |
> but when someone *does* stumble upon such issues, it is up to |
14 |
> maintainers to update portage to prevent the issue... that's what |
15 |
> portage is for, isn't it? |
16 |
> That said, the topic starter has run across an issue and I assume the |
17 |
> action to be taken by the package maintainer is to add a test against |
18 |
> kernel compatibility and eligibility of the native driver, so that in |
19 |
> the future the issue not rise again. Am I right? Or do I completely |
20 |
> misunderstand the purpose of portage, and everything? |
21 |
|
22 |
First of all: Gentoo relies on volunteers to do work as testing. If |
23 |
something fails they CAN report it (like he did via this userlist). |
24 |
You're requesting enterprise features (everything tested to a great |
25 |
extent for every piece of hardware)? That's cool, because you can help. |
26 |
Just invest some time and help testing, everyone would be grateful. |
27 |
Without those reports portage can't know. It's a tool and not a thinking |
28 |
human being, as such it's limited in many ways. How should it know that |
29 |
something will break other things if nobody tells it? |
30 |
|
31 |
>>> 4. How and why would you expect to force all users to grep thru kernel |
32 |
>>> src in search for a driver they might need, especially when the |
33 |
>>> portage explicitly lists this driver? Also sometimes kernel drivers' |
34 |
>>> description is not quite consistent and it is not easy to figure out |
35 |
>>> whether it supports exactly yours card/chip/device, or moreover find |
36 |
>>> it by grep. |
37 |
>> |
38 |
>> All kernel source? grep? Nope. Just reading a bit of help text. Maybe |
39 |
>> using google. Doing it once. |
40 |
> |
41 |
> As I said, there is not always good help text for kernel options. |
42 |
> |
43 |
|
44 |
I tend to agree but then again: why even bother compiling the Linux |
45 |
kernel if it's too tedious? |
46 |
|
47 |
>> Then you have a working setup you can use |
48 |
>> for the rest of eternity (or the next couple of years...) |
49 |
> |
50 |
> Okay, and when someone like the topic starter *did* have a working |
51 |
> setup with the "superfluous" driver from portage, ... do you feel the |
52 |
> logic? :) When should one realize that this setup is no more working? |
53 |
> I guess, just after it stopped working, right? :) Of course, again, if |
54 |
> one is really concerned he will check each kernel release or whatever |
55 |
> for the new stuff he's concerned about, but when all *worked*, why |
56 |
> should he? |
57 |
There are distributions out there who take care of *this*. Instead of |
58 |
utilizing them you're trying to redefine Gentoo in a manner that more |
59 |
suits you. This is highly illogical, as alternatives are out there with |
60 |
the exact same thing you'd like to see. |
61 |
|
62 |
|
63 |
> so, according to that, everyone who's striving to get |
64 |
> linux/gentoo/whtever more user-friendly (including portage's key |
65 |
> features) is an ubuntoid? You know, I came from FreeBSD where you're |
66 |
> supposed to do much more work by hand, and after a dozen years I'm a |
67 |
> little bit tired of that. I *can* do without things like portage's |
68 |
> colorful output, for example (although it's helpful most of the time). |
69 |
> But I really dislike things broken e.g. on `portupgrade -aR` and the |
70 |
> sort and I can *not* call a system which allows that a quality system. |
71 |
> That sort of user-friendliness has nothing to do with ubuntism ("we |
72 |
> know better what you want") and visual beauty: that's about quality. |
73 |
> (I know that there's no absolute quality, but when a system tends to |
74 |
> fail, and justifies that with "user not having googled or having taken |
75 |
> a way we, devs, didn't ever think to go" -- it's at least incorrect if |
76 |
> not arrogant.) |
77 |
|
78 |
You're mixing up Linux and distributions. Linux is a kernel, not more, |
79 |
not less. If the distribution is user friendly or not is defined for |
80 |
every single distribution. |
81 |
The problem I see here: you want Gentoo to do certain things for you |
82 |
which is in direct conflict to Gentoo's principles. Gentoo really was |
83 |
never meant for the beginner, nor was it meant for the expert who just |
84 |
wants to USE things and SOMETIMES change crucial parts of the system. |
85 |
|
86 |
In my personal opinion it's highly arrogant to download a distribution, |
87 |
seeing that you obviously don't like it (which is absolutely fine) and |
88 |
then jump on the mailing list. Patronizing everyone and telling them how |
89 |
that system should exactly change that it's acceptable in your eyes. |
90 |
|
91 |
But, that's the whole beauty of open source: you can do things exactly |
92 |
your way by forking, helping as a dev/tester, developing your own things |
93 |
if you hate them, etc... |
94 |
And before you tell me: "you want to troll me". Nope, I'm dead serious. |
95 |
Open source is all about getting involved if you want to change things. |
96 |
Other certain operating systems don't even give you that choice and are |
97 |
more like: like it or leave it. |