public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users)
Date: Mon, 31 Oct 2005 17:46:36 -0600	[thread overview]
Message-ID: <20051031234636.GA10657@nightcrawler> (raw)
In-Reply-To: <200511010836.29453.chriswhite@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

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.
~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-31 23:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 23:36 [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users) Chris White
2005-10-31 23:41 ` [gentoo-dev] " Dan Meltzer
2005-10-31 23:52   ` Dan Meltzer
2005-11-01  7:56     ` Wernfried Haas
2005-11-01 14:32       ` Chris Gianelloni
2005-11-01 19:32       ` Stuart Herbert
2005-11-01 19:51         ` Chris Gianelloni
2005-11-03 19:40           ` Stuart Herbert
2005-11-04  1:10             ` Nathan L. Adams
2005-11-04  8:22               ` Sami Näätänen
2005-11-04 14:26               ` Xavier Neys
2005-11-04 16:44                 ` Jason Stubbs
2005-11-04 18:53                   ` Alec Joseph Warner
2005-11-05  5:08                     ` Jason Stubbs
2005-11-05  5:34                       ` Alec Warner
2005-11-07 10:11                         ` Paul de Vrieze
2005-11-07 12:37                           ` Jason Stubbs
2005-11-07 16:06                             ` Grant Goodyear
2005-11-07 16:44                               ` Jason Stubbs
2005-11-07 16:43                             ` Stuart Herbert
2005-11-05  9:58                       ` [gentoo-dev] " Duncan
2005-11-05 12:54                       ` [gentoo-dev] " Michiel de Bruijne
2005-11-06 19:32                       ` R Hill
2005-11-01 19:53         ` Mike Williams
2005-10-31 23:46 ` Brian Harring [this message]
2005-11-01 10:51   ` [gentoo-dev] " Jason Stubbs
2005-11-01  0:42 ` Ciaran McCreesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051031234636.GA10657@nightcrawler \
    --to=ferringb@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox