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 1EWgv2-0000Ux-5P for garchives@archives.gentoo.org; Mon, 31 Oct 2005 21:10:16 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j9VL9S9r023122; Mon, 31 Oct 2005 21:09:28 GMT Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.201]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j9VL7gnq026545 for ; Mon, 31 Oct 2005 21:07:43 GMT Received: by xproxy.gmail.com with SMTP id h26so634277wxd for ; Mon, 31 Oct 2005 13:07:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AAYXfparE3biM8AhcaqHxbPfTVg8b1DzVU+o94GTbwZ0VCezYT7vwegSbq1bF6kiBDdHFqI6k0LB7fQ1rqHSBvpd28iIZlQCpVCiMV7u0yJyBFOhTLcHbss8F8gMK4J8iCNDY0ZJ2V2TDk+zCarti88RPLZecCkxkdRdaTCLP8I= Received: by 10.70.131.6 with SMTP id e6mr1932308wxd; Mon, 31 Oct 2005 13:07:42 -0800 (PST) Received: by 10.70.8.15 with HTTP; Mon, 31 Oct 2005 13:07:42 -0800 (PST) Message-ID: Date: Mon, 31 Oct 2005 22:07:42 +0100 From: Frido Ferdinand To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Getting Important Updates To Users In-Reply-To: <82e554630510311256q6af11c0asac769c68b96d4871@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <200510301642.39469.chriswhite@gentoo.org> <4364EC47.8050803@gentoo.org> <1130722932.8550.33.camel@mogheiden.gnqs.org> <1130768528.26789.70.camel@cgianelloni.nuvox.net> <43662CD9.2000405@gentoo.org> <1130777404.10549.16.camel@mogheiden.gnqs.org> <436651B8.2020108@gentoo.org> <1130785533.10547.41.camel@mogheiden.gnqs.org> <20051031200727.GA6968@valinor.wadham.ox.ac.uk> <82e554630510311256q6af11c0asac769c68b96d4871@mail.gmail.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j9VL7gnq026545 X-Archives-Salt: e3b0cd85-3b26-441e-be61-66dd7ceb85e4 X-Archives-Hash: 34950842ec3ef3da742864ffa96a9f0b Hi, On 10/31/05, Dave Shanker wrote: > 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). > Noted this thread on stu's weblog, and found it very interesting. Just jumping in midway, so I might have missed some stuff. I agree that there currently are too many channels where a user could look for information, changing one of these channel to be an authorative one, and start using it more often could be a good solution. However stu's --news proposals looks interesting too, implementation wise maybe it's a good idea to look at the GLSA and GLEP type messages. They provide an excellent fixed, parsable format for changes already. And afaik are the defacto source for security and enhancement proposals. Maybe this should be extended to something like a GLCM (Gentoo Linux Change Message, be creative). if the format is XML defined, i'm sure the portage people can integrate it into emerge --pretend with a special flag, esp. if GLSA is already working. It's also easy to distribute these to websites, mailinglists, RSS etc. As a sideeffect it's also easier to talk about changes (compare, "GLCM 32", to "That apache change earlier this year"). One of the downsides of this could be that it places more work pressure on developers, but i'm sure a good generation tool will help with this. As a sidenote, The FreeBSD /usr/ports/UPGRADING is boring, but it works for me. Regards, Frido -- gentoo-dev@gentoo.org mailing list