1 |
Ciaran McCreesh wrote: |
2 |
> | Which means you won't be able to satisfy your "preemptive" |
3 |
> | requirement. |
4 |
> |
5 |
> Not at all. You can warn users repeatedly, but there comes a point when |
6 |
> trying to warn them any further becomes futile. |
7 |
|
8 |
Then what is the point of this GLEP? Instead, just warn people through |
9 |
existing intrastructure, which is cheap from an engineering perspective |
10 |
because everything is already there in place, and don't think of |
11 |
implementing all kinds of extras just to warn a user one extra time, |
12 |
since "trying to warn them any further becomes futile" anyway. |
13 |
|
14 |
The motivation of your GLEP is based solely on the assumption that |
15 |
critical news is not effectively delivered to the user, however, the |
16 |
GLEP implicitly introduces this critical news, so how can it be ignored |
17 |
by users? It's not there. |
18 |
|
19 |
If you don't plan to solve the requirements you state yourself, either |
20 |
don't state them, or make clear you will not satisfy them for what |
21 |
reason. To me it looks as if you just would like to remove the |
22 |
'preemptive' requirement because it suggests some behaviour that you |
23 |
don't (plan to) implement. And hence, you should also rewrite the |
24 |
motivation to reflect your statement in the quote above. |
25 |
|
26 |
I like the idea of the GLEP, since it will be helpful for many users I |
27 |
think, but the grounds on which and the reasons why should be valid |
28 |
points, IMHO. I also think that the idea comes very close to things |
29 |
proposed and or desired by many users that would like to have all the |
30 |
einfo messages being sent out to them, or accumulated after portage has |
31 |
done it's compiling. See the respective super bug and ml discussions on |
32 |
it. Hence, the GLEP itself doesn't differentiate itself, is not defined |
33 |
to be generic enough or reusable, should include configurability and, |
34 |
last but not least as I mentioned before, should be grounded in valid |
35 |
points. |
36 |
|
37 |
|
38 |
-- |
39 |
Fabian Groffen |
40 |
Gentoo for Mac OS X Project -- Interim Lead |
41 |
-- |
42 |
gentoo-dev@g.o mailing list |