| 1 |
What about Portage auto generating a upgrade file |
| 2 |
(/usr/portage/notices (like it does with it's cache) and then |
| 3 |
providing a notice at the end of an emerge than lets the user know |
| 4 |
it's there and how to read it. We could even provide a switch in |
| 5 |
portage to read the file and display the notices (emerge |
| 6 |
--readnotice). |
| 7 |
|
| 8 |
Regards, |
| 9 |
|
| 10 |
On 10/31/05, David Morgan <david.morgan@××××××××××××××××.uk> wrote: |
| 11 |
> On 19:05 Mon 31 Oct , Stuart Herbert wrote: |
| 12 |
> > > Maybe we could add a big news warning in the next minor portage |
| 13 |
> > > update that when you tells you about the new news features (perhaps a |
| 14 |
> > > big einfo after you upgrade. |
| 15 |
> > |
| 16 |
> > The problems of einfo messages not reaching our users have been well |
| 17 |
> > documented already :( |
| 18 |
> > |
| 19 |
> |
| 20 |
> Why not log all the e{info,warn}s into a file, and then tell the user |
| 21 |
> about them at the end of the emerge (in the same way they are told about |
| 22 |
> changes in /etc)? Said file should then be safe to delete if desired. |
| 23 |
> |
| 24 |
> Mailing this info instead (/as well?) could also be available as an |
| 25 |
> option (even if the user just wants to use something simple like nbsmtp |
| 26 |
> to send it to some email address, rather than having to run their |
| 27 |
> own mailserver). |
| 28 |
> |
| 29 |
> I guess you could also go for something like freebsd's |
| 30 |
> /usr/ports/UPGRADING file, which users are supposed to read before |
| 31 |
> upgrading things, but I'm not sure if people would bother reading it. |
| 32 |
> |
| 33 |
> Dave |
| 34 |
> |
| 35 |
> -- |
| 36 |
> gentoo-dev@g.o mailing list |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives