Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: gentoo-dev@l.g.o, pr@g.o
Subject: Re: [gentoo-dev] openrc portage news item
Date: Fri, 29 Apr 2011 11:22:42
Message-Id: BANLkTinCS_aLBy6jJAyjph_Tj2+o=u4rbw@mail.gmail.com
In Reply to: Re: [gentoo-dev] openrc portage news item by William Hubbs
1 On Fri, Apr 29, 2011 at 3:08 AM, William Hubbs <williamh@g.o> wrote:
2 > Someone suggested that we make emerge not work until the news item is
3 > read. There is nothing I can do in openrc to make something like that
4 > happen. It would be something that would require a portage modification.
5
6 Honestly - I see that as a future enhancement for portage/PMS/etc, and
7 not something that should hold up openrc. There are a number of
8 situations where such a feature would be useful, and trying to
9 shoehorn in a hack for openrc doesn't make sense.
10
11 Perhaps a future/in-progress EAPI could define a mechanism where an
12 ebuild can indicate that a particular update or set of circumstances
13 is a system-critical change, and that the package manager should
14 consequently alert the user and ensure that they have confirmed the
15 action. Then we have a nicely defined interface that we can use for
16 things like major baselayout changes, gcc/glibc ABI changes, and so
17 on.
18
19 Otherwise the best we can do is widely publicize the change (news,
20 lists, website, etc). In this case the news is out a full week before
21 the update, which I think is good timing (long enough that missing it
22 is less likely, not so long that forgetting it is likely).
23
24 Rich

Replies

Subject Author
Re: [gentoo-dev] openrc portage news item Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>