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 <gentoo-dev+bounces-45508-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1QFlmU-0001IY-E5
for garchives@archives.gentoo.org; Fri, 29 Apr 2011 11:22:42 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 2A1F81C03C;
Fri, 29 Apr 2011 11:22:32 +0000 (UTC)
Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181])
by pigeon.gentoo.org (Postfix) with ESMTP id DC4701C030
for <gentoo-dev@lists.gentoo.org>; Fri, 29 Apr 2011 11:21:24 +0000 (UTC)
Received: by wyi11 with SMTP id 11so3719021wyi.40
for <gentoo-dev@lists.gentoo.org>; Fri, 29 Apr 2011 04:21:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type;
bh=etTDOYXrjNf1IsJP7TW32jTGYCyEMSTB1ySO/GgQmGQ=;
b=YgJ7iJBHX03VIFN9+wGI63SyWF4tJQx6QIbqj8FXu3O9o/4zpLIpvcXQDau+QH7aNP
2+pKfTa+DoOAnpIT1tQI8mm3UiW9MTEdIncOjm3kV3tZCVVZtsVeldvZTKGY/v20X7RP
+8g+RAZsu1JW5M6VMu8yX9Cg8ZMbpGN6KyWOw=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type;
b=BCSoXyYQeUfR5lWef2HCiWG+PbQFpiLT8T9r7R1je3dq4da8fx5ce5/ugWnCH8hnoG
I224ouFTI7l1eXOZqPeAi4pm/O/+1h5HpJnAA+wWUh8lFbTBSjbfDCZ3o7QJtydewSIN
Pa8SMoM5NX1sWDy2b/L1w19GPZNWn3buazOL8=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.227.37.220 with SMTP id y28mr711954wbd.82.1304076084024; Fri,
29 Apr 2011 04:21:24 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.227.60.211 with HTTP; Fri, 29 Apr 2011 04:21:23 -0700 (PDT)
In-Reply-To: <20110429070831.GA27531@linux1>
References: <20110413181538.GA2894@linux1>
<20110429070831.GA27531@linux1>
Date: Fri, 29 Apr 2011 07:21:23 -0400
X-Google-Sender-Auth: 9f6doz0MLU4OjzIyUmMm5ODiTYU
Message-ID: <BANLkTinCS_aLBy6jJAyjph_Tj2+o=u4rbw@mail.gmail.com>
Subject: Re: [gentoo-dev] openrc portage news item
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pr@gentoo.org
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt:
X-Archives-Hash: 34f241b1b3d7b998569d849f6d6e9b53
On Fri, Apr 29, 2011 at 3:08 AM, William Hubbs <williamh@gentoo.org> wrote:
> Someone suggested that we make emerge not work until the news item is
> read. There is nothing I can do in openrc to make something like that
> happen. It would be something that would require a portage modification.
Honestly - I see that as a future enhancement for portage/PMS/etc, and
not something that should hold up openrc. There are a number of
situations where such a feature would be useful, and trying to
shoehorn in a hack for openrc doesn't make sense.
Perhaps a future/in-progress EAPI could define a mechanism where an
ebuild can indicate that a particular update or set of circumstances
is a system-critical change, and that the package manager should
consequently alert the user and ensure that they have confirmed the
action. Then we have a nicely defined interface that we can use for
things like major baselayout changes, gcc/glibc ABI changes, and so
on.
Otherwise the best we can do is widely publicize the change (news,
lists, website, etc). In this case the news is out a full week before
the update, which I think is good timing (long enough that missing it
is less likely, not so long that forgetting it is likely).
Rich