From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QCiSH-0008MO-6N for garchives@archives.gentoo.org; Thu, 21 Apr 2011 01:13:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B765C1C038; Thu, 21 Apr 2011 01:13:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 2D3791C025 for ; Thu, 21 Apr 2011 01:12:26 +0000 (UTC) Received: from localhost (174-25-228-204.rstr.qwest.net [174.25.228.204]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: dberkholz) by smtp.gentoo.org (Postfix) with ESMTPSA id D10E91B4065; Thu, 21 Apr 2011 01:12:24 +0000 (UTC) Date: Wed, 20 Apr 2011 20:12:21 -0500 From: Donnie Berkholz To: Kfir Lavi Cc: gentoo-dev@lists.gentoo.org, pr@gentoo.org, William Hubbs Subject: Re: [gentoo-dev] openrc portage news item Message-ID: <20110421011221.GA1736@eee> References: <20110413181538.GA2894@linux1> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: X-Archives-Hash: 95ee3481c7cb64c49fd0b52bc4f1829c --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 13:32 Thu 14 Apr , Kfir Lavi wrote: > When i run world update, I usually don't really check all the written=20 > stuff. >=20 > If I do this, I'm sure a lot more Gentoo users do the same. So do=20 > expect people rebooting the machine without checking what your have=20 > wrote. This can be a major headache if you have few systems that are=20 > doing auto updates. I would solve this issue by stopping the emerge=20 > and getting the attention of the user. If I don't get the attention of=20 > the user, no openrc will be installed. It should be something like=20 > emerge -C ... 1 .2 3 4 5... >=20 > To conclude, you can't issue such a change without proper confirmation fr= om > the user. I know this is the case. You're going to get literally thousands of=20 people (or more) who break their Gentoo systems if that indeed is the=20 consequence of not reading the migration guide and doing some action.=20 =46rom a glance over the guide, it wasn't immediately obvious what in=20 there would result in a broken system. Perhaps it's the "run=20 dispatch-conf" that's buried in the middle of a paragraph without enough=20 emphasis? That's particularly confusing for people who use etc-update=20 instead, and it *needs* to move somewhere more obvious like a separate=20 code listing with big tags and bold text. The line of red=20 text just isn't enough, it needs to stand out even more. It seems like nobody's really clear on what exactly happens though,=20 since I've seen people talking about this *maybe* resulting in an=20 unbootable system. Has anyone tested it? One potential cleaner approach to the same idea Kfir suggested is to=20 make it an interactive emerge with an ACCEPT_LICENSE-like feature that=20 pops up something you must read and agree to. --=20 Thanks, Donnie Donnie Berkholz Sr. Developer, Gentoo Linux Blog: http://dberkholz.com --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAk2vhHIACgkQXVaO67S1rtv3tACg69gX9oWPs25NHIw99xgGMQG/ o5sAn00AxBioHq+rpaN37/tAAbi//yVQ =5/db -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--