| 1 |
Christian Faulhammer <fauli@g.o> writes: |
| 2 |
> Josh Sled <jsled@××××××××××××.org>: |
| 3 |
>> Christian Faulhammer <fauli@g.o> writes: |
| 4 |
>> > see attached test, please review. |
| 5 |
>> |
| 6 |
>> Why not just an elog during install of the emacs-23 package itself? |
| 7 |
> |
| 8 |
> Because nobody reads them |
| 9 |
|
| 10 |
If one doesn't read elog, which is at least put in the terminal during |
| 11 |
the emerge (if not sent to IM or email), why would they read news, which |
| 12 |
they need to go out of their way to find? |
| 13 |
|
| 14 |
> and you get weird errors on start-up which |
| 15 |
> will result in bug reports. |
| 16 |
|
| 17 |
Except this won't get shown until after installation anyways. |
| 18 |
|
| 19 |
Display-If-Installed: =app-editors/emacs-23* |
| 20 |
|
| 21 |
Maybe… |
| 22 |
|
| 23 |
Display-If-Installed: <app-editors/emacs-23 |
| 24 |
|
| 25 |
…instead? To show to those users that are upgrade candidates? |
| 26 |
|
| 27 |
I do wish there was a "pretend/pre-emerge notification" capability in |
| 28 |
portage for things like upgrade guides (libxml, python 2.5->2.6, gnome, |
| 29 |
xorg-1.5, &c.). I guess news gets most of it, and then some. |
| 30 |
|
| 31 |
-- |
| 32 |
...jsled |
| 33 |
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b} |
Archives