| 1 |
Additional issue/question... |
| 2 |
|
| 3 |
On Sat, Nov 05, 2005 at 12:58:14AM +0000, Ciaran McCreesh wrote: |
| 4 |
> 6. Portage filters the news item and, if it is relevant, installs it in a |
| 5 |
> special location to be read by a news item reader. Messages are also |
| 6 |
> displayed to inform the user that news is available. |
| 7 |
> 7. The news item is handled by the user's choice of news item reader. See `News |
| 8 |
> Item Clients`_. |
| 9 |
> |
| 10 |
<snip> |
| 11 |
> |
| 12 |
> Client Side |
| 13 |
> ''''''''''' |
| 14 |
> |
| 15 |
> Notification that new relevant news items will be displayed via the |
| 16 |
> ``emerge`` tool in a similar way to the existing "configuration files need |
| 17 |
> updating" messages: |
| 18 |
> |
| 19 |
> :: |
| 20 |
> |
| 21 |
> * Important: 3 config files in /etc need updating. |
| 22 |
> * Type emerge --help config to learn how to update config files. |
| 23 |
> |
| 24 |
> * Important: there are 5 unread news items. |
| 25 |
> * Type emerge --help news to learn how to read news files. |
| 26 |
> |
| 27 |
> The unread news message will also be displayed immediately after an |
| 28 |
> ``emerge sync``. |
| 29 |
|
| 30 |
Your example readers delete from the news directory, yet I'd expect |
| 31 |
that's not going to be desirable for all setups- nor is leaving the |
| 32 |
news item in the news directory, and having it flagged every sync by |
| 33 |
emerge as unread. |
| 34 |
|
| 35 |
Might want to consider some way to mark an item as read without waxing |
| 36 |
it from the directory, if against it, clarify in the glep why. |
| 37 |
~harring |
Archives