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 1EXfR5-0007cA-Df for garchives@archives.gentoo.org; Thu, 03 Nov 2005 13:47:23 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jA3DkBVG013074; Thu, 3 Nov 2005 13:46:11 GMT Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jA3DiDLe004972 for ; Thu, 3 Nov 2005 13:44:14 GMT Received: from [67.191.242.121] (c-67-191-242-121.hsd1.ga.comcast.net[67.191.242.121]) by comcast.net (sccrmhc14) with ESMTP id <2005110313441201400eojc4e>; Thu, 3 Nov 2005 13:44:12 +0000 Message-ID: <436A13AA.1010603@ieee.org> Date: Thu, 03 Nov 2005 08:42:02 -0500 From: "Nathan L. Adams" User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050722) X-Accept-Language: en-us, en 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Getting Important Updates To Users 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> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 68786e39-dc84-415d-a9e0-3534e2aa6c67 X-Archives-Hash: e0a115d0723d9d96c950cbf5c0ed8009 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Duncan wrote: > Stuart Herbert posted <1130785533.10547.41.camel@mogheiden.gnqs.org>, > excerpted below, on Mon, 31 Oct 2005 19:05:33 +0000: > >>The original problem is that GWN, forums, planet.g.o, gentoo-dev - even >>together, we've seen that they just don't reach enough of our user base. >>Aren't we just going to reach the same people by putting more news in >>the same old place? How is that going to reach the people we're not >>reaching today? > > > There is /one/ way to reach /everyone/ doing an upgrade (well, those that > do emerge -a or -p, anyway, and those that don't, well... they apparently > /like/ being left in the dark, and doing perhaps risky upgrades without > knowing what's going on, so let's not disturb their "enjoyment" ). > > That ONE way: Push a "null" portage -rX upgrade to both stable and ~ > versions, the sole purpose of which is to print the *VITALLY* *IMPORTANT* > *ANNOUNCEMENT* as an einfo both after the "upgrade", and as part of the > "portage will stop merging at this point and recalculate" message one gets > with a -p or -a. (For double-sure effect, make the first emerge action > after the upgrade /only/ print the message, doing nothing else. Further > emerges would then go back to normal behavior.) > Cramming this info in portage is stupid, because portage is supposed to be NON-interactive. Does anyone really expect users to sit and stare at the output of a compile (openoffice takes HOURS to compile) waiting for an einfo to pass by? Perhaps printing out an URI after portage is done would be useful: http://errata.g.o/apache-migration.xml Publishing the info on a webpage also allows you to view the info from another computer if you seriously b0rk something during an upgrade. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDahOq2QTTR4CNEQARAg/mAJ9/Lbfpq0McjxI3isOopxLo60q1ugCdH5Ux ++iU1lMgWKCaxgybqQzUdIs= =B+rI -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list