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 1QAKLd-0005kU-F7 for garchives@archives.gentoo.org; Thu, 14 Apr 2011 11:04:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B5D741C08B; Thu, 14 Apr 2011 11:04:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 8DAA61C0CC for ; Thu, 14 Apr 2011 11:03:41 +0000 (UTC) Received: from [192.168.1.201] (215.150.222.87.dynamic.jazztel.es [87.222.150.215]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 800291B4005 for ; Thu, 14 Apr 2011 11:03:40 +0000 (UTC) Subject: Re: [gentoo-dev] openrc portage news item From: Pacho Ramos To: gentoo-dev@lists.gentoo.org In-Reply-To: <1862409.dc8aBZ6kWJ@ugly-elf> References: <20110413181538.GA2894@linux1> <1862409.dc8aBZ6kWJ@ugly-elf> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-qWHtgfaF6f6XzK3IDV5w" Date: Thu, 14 Apr 2011 13:03:35 +0200 Message-ID: <1302779015.6781.11.camel@localhost.localdomain> 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 X-Mailer: Evolution 2.32.2 X-Archives-Salt: X-Archives-Hash: 48a41c07b039483c1bcd4d7f798ab45c --=-qWHtgfaF6f6XzK3IDV5w Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El jue, 14-04-2011 a las 12:51 +0200, Tom=C3=A1? Chv=C3=A1tal escribi=C3=B3= : > On Thursday 14 of April 2011 13:32:04 Kfir Lavi wrote: > > When i run world update, I usually don't really check all the written s= tuff. > >=20 > > If I do this, I'm sure a lot more Gentoo users do the same. > > So do expect people rebooting the machine without checking what your ha= ve > > wrote. > > This can be a major headache if you have few systems that are doing aut= o > > updates. > > I would solve this issue by stopping the emerge and getting the attenti= on of > > the user. > > If I don't get the attention of the user, no openrc will be installed. > > It should be something like emerge -C ... 1 .2 3 4 5... > >=20 > > To conclude, you can't issue such a change without proper confirmation = from > > the user. > >=20 > This was discussed multiple times, news items are to be read. > Users ignore elog informations/web announcements/... so it was agreed tha= t=20 > news item is agressive enough to user so they must read it. > If they don't do so it is just their fault. > And no runtime changing for portage where it expect some input is serious= ly=20 > stupid idea, most of us script updates in batch and noone would actualy r= ead=20 > it. >=20 > Never the less as I said we expect user to read that stuff and if he does= not=20 > he is on his own due to his dumb approach. I also thought about this problem: I usually read news items before updating, but I have also seen how other people with root access to other machines I mainly maintain forget from time to time to do so.=20 This is why I opened: http://bugs.gentoo.org/show_bug.cgi?id=3D363567 As news items are really there to be read BEFORE updating, I think that it should be enforced to prevent people from updating before reading them (I have also read Lars comment, I obviously have no problem at all with adding some option to revert this behavior, but I still think default behavior should be to prevent update if news items are not read). --=-qWHtgfaF6f6XzK3IDV5w Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk2m1IcACgkQCaWpQKGI+9SY0wCfXYxluW9p2g5f/5jD5uPj1EXH BEQAnRVT+NIwYv02UNr/9Pp6HkFnNchU =9sPj -----END PGP SIGNATURE----- --=-qWHtgfaF6f6XzK3IDV5w--