From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org, pr@gentoo.org
Subject: Re: [gentoo-dev] openrc portage news item
Date: Fri, 29 Apr 2011 07:21:23 -0400 [thread overview]
Message-ID: <BANLkTinCS_aLBy6jJAyjph_Tj2+o=u4rbw@mail.gmail.com> (raw)
In-Reply-To: <20110429070831.GA27531@linux1>
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
next prev parent reply other threads:[~2011-04-29 11:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 18:15 [gentoo-dev] openrc portage news item William Hubbs
2011-04-13 18:27 ` Thomas Beierlein
2011-04-13 18:32 ` justin
2011-04-13 18:41 ` "Paweł Hajdan, Jr."
2011-04-13 19:58 ` William Hubbs
2011-04-14 8:09 ` [gentoo-dev] " Duncan
2011-04-14 11:44 ` Rich Freeman
2011-04-15 14:04 ` Peter Hjalmarsson
2011-04-15 19:01 ` Duncan
2011-04-13 19:56 ` [gentoo-dev] " William Hubbs
2011-04-14 5:30 ` justin
2011-04-14 7:21 ` Dirkjan Ochtman
2011-04-14 8:19 ` justin
2011-04-14 8:40 ` [gentoo-dev] " Duncan
2011-04-14 14:44 ` Dale
2011-04-14 15:41 ` Matthew Summers
2011-04-14 16:12 ` Dale
2011-04-14 18:48 ` William Hubbs
2011-04-14 10:32 ` [gentoo-dev] " Kfir Lavi
2011-04-14 10:32 ` Kfir Lavi
2011-04-14 10:51 ` Tomá? Chvátal
2011-04-14 11:03 ` Pacho Ramos
2011-04-14 11:21 ` Thomas Beierlein
2011-04-14 11:27 ` Sylvain Alain
2011-04-21 1:12 ` Donnie Berkholz
2011-04-21 2:23 ` Jeroen Roovers
2011-04-21 2:34 ` Jeroen Roovers
2011-04-22 10:39 ` Lars Wendler
2011-04-29 18:41 ` Brian Harring
2011-04-30 2:19 ` William Hubbs
2011-04-30 4:59 ` Brian Harring
2011-04-30 7:13 ` [gentoo-dev] " Duncan
2011-04-30 11:46 ` Brian Harring
2011-04-30 12:03 ` Rich Freeman
2011-04-30 12:58 ` Brian Harring
2011-04-30 13:06 ` Jeremy Olexa
2011-04-30 13:40 ` Brian Harring
2011-04-29 7:08 ` [gentoo-dev] " William Hubbs
2011-04-29 11:21 ` Rich Freeman [this message]
2011-04-29 11:28 ` Ciaran McCreesh
2011-04-29 17:18 ` Alex Alexander
2011-04-29 17:25 ` Ulrich Mueller
2011-04-29 17:32 ` Alex Alexander
2011-04-29 17:52 ` Rich Freeman
2011-04-29 17:58 ` Alex Alexander
2011-04-30 0:34 ` William Hubbs
2011-04-30 9:04 ` Sergei Trofimovich
2011-04-30 12:41 ` Roy Bamford
2011-04-29 14:27 ` [gentoo-dev] " Duncan
2011-05-01 19:12 ` [gentoo-dev] " William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTinCS_aLBy6jJAyjph_Tj2+o=u4rbw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox