| 1 |
1.11.2005, 13:26:57, Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
> On Tue, 01 Nov 2005 13:16:03 +0100 Thierry Carrez <koon@g.o> |
| 4 |
> wrote: |
| 5 |
> | For them to know about it, they need to be warned when they do their |
| 6 |
> | "emerge -p world" or "emerge -a mysql" that the upgrade is not as easy |
| 7 |
> | as it seems. People using a cron job to sync are probably a |
| 8 |
> | significant part of our user base... |
| 9 |
|
| 10 |
> Have Portage give a red flashy before emerge if there're unread news |
| 11 |
> items? |
| 12 |
|
| 13 |
> Although, a better solution for users who cron sync would be to have |
| 14 |
> said cron mail them all the relevant news files... |
| 15 |
|
| 16 |
Uhm... emerge sync is a *bad* time to display upgrade messages, it's simply |
| 17 |
irrelevant at that time, I'm not upgrading anything at the moment and might not |
| 18 |
be upgrading for next week or so. |
| 19 |
|
| 20 |
The messages should be displayed when I'm about to upgrade an ebuild which has |
| 21 |
an upgrade note associated with the new version. Sending mail via cron might be |
| 22 |
a nice optional feature for those who want to use it. |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
|
| 27 |
Jakub Moc |
| 28 |
mailto:jakub@g.o |
| 29 |
GPG signature: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xCEBA3D9E |
| 30 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
| 31 |
|
| 32 |
... still no signature ;) |
Archives