| 1 |
On Tuesday 01 November 2005 02:00, Thierry Carrez wrote: |
| 2 |
> Ciaran McCreesh wrote: |
| 3 |
> > Notification that new relevant news items will be displayed via the |
| 4 |
> > ``emerge`` tool in a similar way to the existing "configuration files |
| 5 |
> > need updating" messages: |
| 6 |
> > |
| 7 |
> > * Important: 3 config files in /etc need updating. |
| 8 |
> > * Type emerge --help config to learn how to update config files. |
| 9 |
> > |
| 10 |
> > * Important: there are 5 unread news items. |
| 11 |
> > * Type emerge --help news to learn how to read news files. |
| 12 |
> |
| 13 |
> Aren't those messages displayed after the damage is done ? Typical use : |
| 14 |
> |
| 15 |
> - emerge --sync run as a daily cron job |
| 16 |
> - emerge -a mysql |
| 17 |
> - great, a new version is there. Typing "Yes" |
| 18 |
> - system gets borken |
| 19 |
> - emerge spits out message saying 14 files need updating and there is 1 |
| 20 |
> unread news item |
| 21 |
> |
| 22 |
> I'm probably missing something here. Please elaborate on how this GLEP |
| 23 |
> meets the "Preemptive" design goal... |
| 24 |
The "configuration files need updating" messages also appear at the end of |
| 25 |
emerge sync |
| 26 |
|
| 27 |
Also, perhaps the news messages could be put at both ends of the emerge |
| 28 |
output? |
Archives