public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michiel de Bruijne <m.debruijne@hccnet.nl>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 42 (Was: Getting Important Updates To Users)
Date: Sat, 5 Nov 2005 13:54:44 +0100	[thread overview]
Message-ID: <200511051354.44611.m.debruijne@hccnet.nl> (raw)
In-Reply-To: <200511051408.09014.jstubbs@gentoo.org>

On Saturday 05 November 2005 06:08, Jason Stubbs wrote:
> Why does `emerge --changelog` not suffice for package-specific news?

>From a user/sys.admin point of view let me give you an example;

I maintain quite a lot Gentoo-systems. For me it's impossible to read _every_ 
changelog for minor release changes. For example not so long ago Apache was 
upgraded from 2.0.54-r15 to 2.0.54-r31. For me as a user/sys.admin based on 
versionnumbers this is a minor change. However the changes were rather 
extensive (e.g. reorganization of conf.files). 

When these changes occur I want to be informed _before_ I start emerge and I 
think that this information should be _pushed_ to users/sys.admins instead of 
_pulled_ from external sources (forums, website, mailinglist, etc. or 
changelogs).

If changelogs could be extended with a priority flag and emerge would notify 
me when a high priority changelog is applicable to my system then this would 
be just fine for me. Basically all I want is;

Notification that new relevant news items will be displayed via the
``emerge`` tool in a similar way to the existing "configuration files need
updating" messages:

::

    * Important: 3 config files in /etc need updating.
    * Type emerge --help config to learn how to update config files.

    * Important: there are 2 security advisories released for installed 
packages.
    * Type emerge --security to see the details.

    * Important: there are 5 unread news items.
    * Type emerge --help news to learn how to read news files.

If this is possible by extending the changelog I'm a happy users/sys.admin. I 
don't care if I need to type emerge --news or emerge --changelog as long the 
information is pushed.


Disclaimer; I'm not 100% sure that the versionnumbers from Apache mentioned 
above are exact the real world examples, but you get the idea.

Regards,

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-11-05 12:57 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                       ` Michiel de Bruijne [this message]
2005-11-06 19:32                       ` [gentoo-dev] " R Hill
2005-11-01 19:53         ` Mike Williams
2005-10-31 23:46 ` [gentoo-dev] " Brian Harring
2005-11-01 10:51   ` 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=200511051354.44611.m.debruijne@hccnet.nl \
    --to=m.debruijne@hccnet.nl \
    --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