Re: [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users)

[Jason Stubbs <jstubbs@gentoo.org>]

On Tuesday 01 November 2005 08:46, Brian Harring wrote:
> On Tue, Nov 01, 2005 at 08:36:23AM +0900, Chris White wrote:
> > Attached in plain text form is glep 42 for the discussed thread.
> > emerge --news support
> > ---------------------
> >
> > As already mentioned by Stuart, in this way users are bound to the one
> > thing guaranteed on their system: Portage.  Through portage, the same
> > location where etc-update notifications are displayed (after emerge
> > --sync and at the finish of an emerge), will contain a notice about news
> > updates.  These news updates should come in the form of a file contained
> > within the portage tree for users that want news updates on a networkless
> > system. Should the user run these items in the background or send the
> > output to /dev/null for any reason, a --news option should also be
> > avaliable in emerge for them to review the news at a convient time.
>
> And this file is what format?  How is the format going to be
> structured so that emerge can know what entries to ignore?  How is
> emerge going to pull those entries again?
>
> What restrictions are there for what goes into this file, to keep the
> signal to noise ratio sane?
> Etc.
>
> Details man, details.

But before details, what is the reasoning in turning emerge into an offline 
news reader? So that admins that don't care enough to source news information 
via other supported means are covered? What's the functional difference 
between this "emerge --news" and the existing "emerge --changelog"? I'd like 
bugs to be better described; should a tutorial be added to emerge as well?

--
Jason Stubbs
-- 
gentoo-dev@gentoo.org mailing list