1 |
On Sat, 5 May 2007 00:52:46 +0100 |
2 |
Ciaran McCreesh <ciaranm@×××××××.org> wrote: |
3 |
|
4 |
> On Fri, 4 May 2007 19:48:19 -0400 |
5 |
> Dan Meltzer <hydrogen@×××××××××××××××××.com> wrote: |
6 |
> > That seems like a really bad road to go down. |
7 |
> > |
8 |
> > Would it not be better to extend elog to alert people at the end of |
9 |
> > an install as well? |
10 |
> |
11 |
> Doesn't help. It's only there once, and it's easy to ignore. Users |
12 |
> don't have to explicitly mark it as read, so it's frequently not read. |
13 |
> elog is not an adequate solution. |
14 |
|
15 |
Interesting that so far nobody (including yourself) has requested such a |
16 |
feature ... |
17 |
Also GLEP42 (as specified) is also an inadequate solution as there is |
18 |
no check for news items _after_ a package install, so in the typical |
19 |
use case users won't see this news item when it's most relevant (going |
20 |
by specification, haven't checked implementations). |
21 |
And given that the GLEP specifically states that news items are not |
22 |
suposed to replace the usual postinst einfo/elog messages I'm tempted to |
23 |
call this an abuse of the news framework. |
24 |
|
25 |
Marius |
26 |
|
27 |
-- |
28 |
Public Key at http://www.genone.de/info/gpg-key.pub |
29 |
|
30 |
In the beginning, there was nothing. And God said, 'Let there be |
31 |
Light.' And there was still nothing, but you could see a bit better. |