| 1 |
On Mon, Jul 5, 2010 at 7:53 AM, Richard Freeman <rich0@g.o> wrote: |
| 2 |
> On 07/04/2010 04:09 PM, Jory A. Pratt wrote: |
| 3 |
>> |
| 4 |
>> For those of you not on the #gentoo-dev channel, I just announced I am |
| 5 |
>> gonna be looking at the openrc code and fixing the bugs and working to |
| 6 |
>> continue the development. Anyone that is interested in helping please |
| 7 |
>> feel free to contact me off list to discuss how we will handle getting |
| 8 |
>> openrc back on track. |
| 9 |
>> |
| 10 |
> |
| 11 |
> Well, openrc isn't any worse than baselayout-1 for upstream support. |
| 12 |
> However, I do agree that we should strongly try to standardize on something |
| 13 |
> that is more cross-platform if possible. |
| 14 |
> |
| 15 |
> I'd rather not push to make openrc stable (which means lots of migration for |
| 16 |
> users), only to then move to something else anyway. Why have two migrations |
| 17 |
> when you can just have one? |
| 18 |
> |
| 19 |
|
| 20 |
The reason why people want to do an openrc migration right now is |
| 21 |
because we don't know when we'll find something else to move to; make |
| 22 |
it work with gentoo, make it work for everyone, iron out all the bugs, |
| 23 |
and push it to stable. In all probability, and looking at our past |
| 24 |
experience with pushing openrc to stable, it *will* take years. It's |
| 25 |
too much work to maintain both baselayout-1 *and* openrc *and* find |
| 26 |
something else to move to. It's best to move to openrc (which has |
| 27 |
numerous benefits over baselayout-1, and has a maintainer now), and |
| 28 |
then see what we can do. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
~Nirbheek Chauhan |
| 33 |
|
| 34 |
Gentoo GNOME+Mozilla Team |
Archives