1 |
Mike Frysinger wrote: |
2 |
> |
3 |
> |
4 |
> i really dont buy this argument, but ignoring that, poor admin policy is no |
5 |
> excuse. blindly accepting all unstable versions of a package instead of |
6 |
> pinning a specific version and then expecting a stable system isnt going to |
7 |
> happen. Thomas is absolutely right here. |
8 |
> |
9 |
> |
10 |
Well, if eh is absolutely right, then I won't argue anymore. |
11 |
|
12 |
But just as an notice, I didn't expect STABLE but at least DOCUMENTED |
13 |
system ? |
14 |
Is that too much to ask ? |
15 |
|
16 |
And even if I did a mistake of keywording openrc-0* instead of |
17 |
openrc-0.4-r3, do I really deserve such knife in the back ? |
18 |
|
19 |
Having some reasonable safety margin is base of sanity. Your PSU is |
20 |
galvanicaly insulated, but law demands that housing of your PC be |
21 |
connected to earth potential in case of insulation failing. Had that |
22 |
been done by Gentoo community courts would be full of cases of |
23 |
"unreasonable dead jerks who should be grateful"... |
24 |
|
25 |
|
26 |
> documentation doesnt write itself. this isnt directed specifically at you, |
27 |
> but clamoring "gimme gimme gimme" is more likely to get people to tell you to |
28 |
> toss off than get what you want. |
29 |
And who should write documentation for new code ? Unreasonable users |
30 |
that find it not working or perhaps authors ? |
31 |
While I recognise the fact that Gentoo is not commercial distro, I want |
32 |
also some recognition for value of my time as a passive tester. |
33 |
|
34 |
I am happy to give what I can, but I expect at least some basic |
35 |
foundations for that. Having documentation about public changes at least |
36 |
for me falls well within that category. |
37 |
|
38 |
At least for me, even otherwise useful changes can have NEGATIVE value, |
39 |
if they gob heaps of my time totally unnecesarilly and total lack of |
40 |
documentation is on top of the list of best ways to piss on masses. |