From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EWwNn-0005ec-Ol for garchives@archives.gentoo.org; Tue, 01 Nov 2005 13:41:00 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA1Dcvb2001915; Tue, 1 Nov 2005 13:38:57 GMT Received: from egr.msu.edu (jeeves.egr.msu.edu [35.9.37.127]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA1DYD9a008509 for <gentoo-dev@lists.gentoo.org>; Tue, 1 Nov 2005 13:34:14 GMT Received: from [35.13.37.30] (13-37-30.client.wireless.msu.edu [35.13.37.30]) by egr.msu.edu (8.13.4/8.13.4) with ESMTP id jA1DYD4t018593 for <gentoo-dev@lists.gentoo.org>; Tue, 1 Nov 2005 08:34:13 -0500 (EST) Message-ID: <43676EE1.2080307@egr.msu.edu> Date: Tue, 01 Nov 2005 08:34:25 -0500 From: Alec Warner <warnera6@egr.msu.edu> User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] GLEP ??: Critical News Reporting References: <20051101015125.1cc45eb4@snowdrop.home> <43673CB6.1010907@gentoo.org> <20051101115843.7b2dfeeb@snowdrop.home> <43675C83.4010005@gentoo.org> <20051101122657.2d06d9e5@snowdrop.home> <11710324670.20051101133924@gentoo.org> <20051101124806.422976f6@snowdrop.home> In-Reply-To: <20051101124806.422976f6@snowdrop.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: fceb9d21-da72-4138-860c-f0079f409fb1 X-Archives-Hash: cc62cd3c2e8e294d908fe9a970809f85 Ciaran McCreesh wrote: >On Tue, 1 Nov 2005 13:39:24 +0100 Jakub Moc <jakub@gentoo.org> wrote: >| Uhm... emerge sync is a *bad* time to display upgrade messages, it's >| simply irrelevant at that time, I'm not upgrading anything at the >| moment and might not be upgrading for next week or so. > >It doesn't display the messages. It displays a note saying "you have >unread news items". > >| The messages should be displayed when I'm about to upgrade an ebuild >| which has an upgrade note associated with the new version. Sending >| mail via cron might be a nice optional feature for those who want to >| use it. > >Not really a good idea, a) because news items aren't tied directly to >ebuilds, and b) because people like advance warning of "when you >upgrade Apache, all hell will break loose!" rather than having it >sprung on them suddenly when they're trying to do a quick update. >Getting the news item in advance allows for planning. > > > Personally, I'm for both. E-mailing cron output is a relatively simple operation. Adding a red flashy deal to emerge saying hey, package X has an unread news item, also simple as long as the read/unread format is non-complex. Having emerge --news, I dislike emmensely. We have emerge --changelog, and contrary to what someone posted above, it shows up whenever you specify -l. However changelog does have it's fair share of problems, mostly people who don't use the correct changelog format and break the tagging, causing -l to display nothing. If you want to make a seperate program to read the news, go for it. I don't see why we have to stick silly things in a core utility. emerge is a package manager, it does not do your laundry too. -Alec Warner (Antarus) -- gentoo-dev@gentoo.org mailing list