What about Portage auto generating a upgrade file
(/usr/portage/notices (like it does with it's cache) and then
providing a notice at the end of an emerge than lets the user know
it's there and how to read it. We could even provide a switch in
portage to read the file and display the notices (emerge
--readnotice).
Regards,
On 10/31/05, David Morgan <[EMAIL PROTECTED]> wrote:
> On 19:05 Mon 31 Oct , Stuart Herbert wrote:
> > > Maybe we could add a big news warning in the next minor portage
> > > update that when you tells you about the new news features (perhaps a
> > > big einfo after you upgrade.
> >
> > The problems of einfo messages not reaching our users have been well
> > documented already :(
> >
>
> Why not log all the e{info,warn}s into a file, and then tell the user
> about them at the end of the emerge (in the same way they are told about
> changes in /etc)? Said file should then be safe to delete if desired.
>
> Mailing this info instead (/as well?) could also be available as an
> option (even if the user just wants to use something simple like nbsmtp
> to send it to some email address, rather than having to run their
> own mailserver).
>
> I guess you could also go for something like freebsd's
> /usr/ports/UPGRADING file, which users are supposed to read before
> upgrading things, but I'm not sure if people would bother reading it.
>
> Dave
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
gentoo-dev@gentoo.org mailing list
