public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jory A. Pratt" <anarchy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: The future of sys-apps/openrc in Gentoo
Date: Sun, 04 Jul 2010 15:09:45 -0500	[thread overview]
Message-ID: <4C30EA89.4020806@gentoo.org> (raw)
In-Reply-To: <20100704133949.0cda055a@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/04/2010 02:39 PM, Ryan Hill wrote:
> On Sun, 4 Jul 2010 17:17:25 +0200
> Fabio Erculiani <lxnay@gentoo.org> wrote:
> 
>> How are we supposed to handle the amount of installations out there
>> that are using OpenRC then?
>> OpenRC/bl-2 have proven to be a big improvement over the old stuff. I
>> am for fixing current bugs, and keep it maintenance mode at least.
>> I'm already spread over several things but I could give a hand to
>> other devs willing to take over.
> 
> 
> http://archives.gentoo.org/gentoo-dev/msg_21f716d5ffa6f04520e39d12fbe43452.xml
> 
>> The only reason why OpenRC has not come up for stabilization by it's
>> maintainers is the fact that everytime there's a new version readied
>> for release, on the horizon there's new incompatible changes being
>> planned for the next version. The OpenRC maintainers in Gentoo have
>> always chosen to wait until OpenRC settles down a little bit. Now with
>> the plan to drop support for certain features (ADSL and PPP support in
>> the networking code), it's going to rewrite more Gentoo people to step
>> up to develop and maintain this code.
> 
> 
> I would say it's settled down now.
> 
> I don't think stable can wait another 2-3 years on baselayout-1 while we
> switch to yet another rc system.
> 
> 
For those of you not on the #gentoo-dev channel, I just announced I am
gonna be looking at the openrc code and fixing the bugs and working to
continue the development. Anyone that is interested in helping please
feel free to contact me off list to discuss how we will handle getting
openrc back on track.

- -- 
======================================================
Jory A. Pratt                  anarchy -at- gentoo.org
Gentoo Mozilla Lead
GPG: 2C1D 6AF9 F35D 5122 0E8F 9123 C270 3B43 5674 6127
======================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkww6okACgkQwnA7Q1Z0YSdhmQCgkKbxZtEX+xZ5EctZYMJ3gegR
w30AnidMZVVlTY6OLJ2/vR8dr9wQ/lRD
=F1WI
-----END PGP SIGNATURE-----



  reply	other threads:[~2010-07-04 20:11 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-04 14:29 [gentoo-dev] The future of sys-apps/openrc in Gentoo Lars Wendler
2010-07-04 15:01 ` [gentoo-dev] " Nikos Chantziaras
2010-07-04 18:23   ` Daniel Schömer
2010-07-04 15:17 ` [gentoo-dev] " Fabio Erculiani
2010-07-04 18:35   ` Markos Chandras
2010-07-04 19:39   ` [gentoo-dev] " Ryan Hill
2010-07-04 20:09     ` Jory A. Pratt [this message]
2010-07-05  2:23       ` Richard Freeman
2010-07-05  3:32         ` Nirbheek Chauhan
2010-07-05  8:57           ` Duncan
2010-08-23 15:05             ` Gilles Dartiguelongue
2010-08-23 15:16               ` Jory A. Pratt
2010-08-23 16:25               ` Mike Frysinger
2010-08-23 17:26               ` Olivier Crête
2010-08-23 18:09                 ` Mike Auty
2010-08-23 18:28                   ` Olivier Crête
2010-08-23 18:43                     ` Patrick McLean
2010-08-24  9:19                 ` Patrick Lauer
2010-08-24 12:57                   ` Thilo Bangert
2010-08-24 14:30                     ` Richard Freeman
2010-08-24 16:38                       ` Joshua Saddler
2010-08-24 17:18                         ` Christian Faulhammer
2010-08-25  3:21                           ` Joshua Saddler
2010-08-25  3:57                             ` Nathan Zachary
2010-08-25  4:14                               ` Joshua Saddler
2010-08-25 16:37                               ` Richard Freeman
2010-08-25 19:06                                 ` Mike Frysinger
2010-08-25 20:16                                   ` Richard Freeman
2010-08-26  0:29                                     ` Duncan
2010-08-26 17:02                                       ` Richard Freeman
2010-08-26 18:29                                         ` Mike Frysinger
2010-08-27  1:55                                           ` Duncan
2010-08-24 16:19                     ` Mike Frysinger
2010-08-24 19:07                       ` Thilo Bangert
2010-07-05 13:03           ` Anthony G. Basile
2010-07-04 16:28 ` [gentoo-dev] " Pacho Ramos
2010-07-04 21:02 ` Mike Frysinger
2010-07-04 22:04   ` Lars Wendler
2010-07-04 22:15     ` Mike Frysinger
2010-07-04 23:23       ` Lars Wendler
2010-07-05  1:03       ` Olivier Crête
2010-07-05  1:30         ` Brian Harring
2010-07-05 16:11           ` Enrico Weigelt
2010-07-05  3:23         ` Mike Frysinger
2010-07-05  4:13         ` Nirbheek Chauhan
2010-07-05 16:13           ` Enrico Weigelt
2010-07-07  0:56             ` Doug Goldstein
2010-07-05  7:29         ` Patrick Lauer
2010-08-23 14:17         ` Jon Portnoy
2010-08-23 20:21         ` Luca Barbato
2010-08-23 20:30           ` Anthony G. Basile
2010-08-23 21:07           ` Mike Frysinger
2010-08-24  9:08             ` Luca Barbato

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=4C30EA89.4020806@gentoo.org \
    --to=anarchy@gentoo.org \
    --cc=gentoo-dev@lists.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