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 1EWgjs-0001Xc-Eo for garchives@archives.gentoo.org; Mon, 31 Oct 2005 20:58:44 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j9VKvvwc018075; Mon, 31 Oct 2005 20:57:57 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j9VKu8Cu015945 for ; Mon, 31 Oct 2005 20:56:09 GMT Received: by wproxy.gmail.com with SMTP id 71so477777wri for ; Mon, 31 Oct 2005 12:56:08 -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=G9wwdWDcLuLhQB3g4V66wCYatOpVSNSTw0mOnzh5T/9t+f3XI5cIuuWsKC7euQoX78QGPLlYJE7BPom29MtEyIPW1xs4FOgnJAx91yvPqLP9oU2fGe2iKV/Kga+rfZ1lg1y/aMEPFpXueScM6fwYUHHpPXQYpDMRv9PbRypJyM4= Received: by 10.54.141.20 with SMTP id o20mr1006619wrd; Mon, 31 Oct 2005 12:56:08 -0800 (PST) Received: by 10.54.70.11 with HTTP; Mon, 31 Oct 2005 12:56:08 -0800 (PST) Message-ID: <82e554630510311256q6af11c0asac769c68b96d4871@mail.gmail.com> Date: Mon, 31 Oct 2005 15:56:08 -0500 From: Dave Shanker To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Getting Important Updates To Users In-Reply-To: <20051031200727.GA6968@valinor.wadham.ox.ac.uk> 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> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j9VKu8Cu015945 X-Archives-Salt: dd0a29e8-5b19-4b59-aae8-41eee2b1390f X-Archives-Hash: 8ecaf8a569d9a69f7bd6dd9dcf969099 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). Regards, On 10/31/05, David Morgan wrote: > On 19:05 Mon 31 Oct , Stuart Herbert wrote: > > > Maybe we could add a big news warning in the next minor portage > > > update that when you tells you about the new news features (perhaps a > > > big einfo after you upgrade. > > > > The problems of einfo messages not reaching our users have been well > > documented already :( > > > > Why not log all the e{info,warn}s into a file, and then tell the user > about them at the end of the emerge (in the same way they are told about > changes in /etc)? Said file should then be safe to delete if desired. > > Mailing this info instead (/as well?) could also be available as an > option (even if the user just wants to use something simple like nbsmtp > to send it to some email address, rather than having to run their > own mailserver). > > I guess you could also go for something like freebsd's > /usr/ports/UPGRADING file, which users are supposed to read before > upgrading things, but I'm not sure if people would bother reading it. > > Dave > > -- > gentoo-dev@gentoo.org mailing list > > -- gentoo-dev@gentoo.org mailing list