1 |
Robert Buchholz wrote: |
2 |
> On Saturday 23 May 2009, Roy Marples wrote: |
3 |
>> Basically as Doug said, each OpenRC version comes with a few big |
4 |
>> chances. Well not massive as in "your box will break now", but just a |
5 |
>> different spin on how things should work. OpenRC-0.5 will have the |
6 |
>> biggest re-spin to date - net.lo (net.eth0 etc) is considered |
7 |
>> deprecated. |
8 |
> |
9 |
> If future changes of this magnitude are still expected, I wonder if we |
10 |
> want to go stable with OpenRC anytime soon. I do not intend to hinder |
11 |
> fast progress and design changes in OpenRC in any way, but if its |
12 |
> design is not considered final, I suggest we do not make it the default |
13 |
> recommandation for our users. |
14 |
|
15 |
Let us be clear on one point - net.lo and friends are still somewhat |
16 |
supported upstream, just no future development will take place on them. |
17 |
|
18 |
The network script is just the preferred default as it makes my life a |
19 |
lot easier and places the support burden onto the maintainers of the |
20 |
various utils needed to be used directly. It's also a lot faster :) |
21 |
|
22 |
I don't expect any more userland changes before the move to OpenRC-1.0 |
23 |
There are two features on the cards - rc events [1] and feature removal |
24 |
for space limited embedded systems (basically dependecy is only used to |
25 |
order scripts on initial startup, reducing /sbin/rc and /sbin/runscript |
26 |
to shell stubs the aim on saving 75k on the binary size. |
27 |
|
28 |
> Marking it stable might also be contraproductive for upstream since |
29 |
> revised configurations need to stay supported a lot longer than they |
30 |
> would had they been used only by ~arch users. |
31 |
|
32 |
If there is a real drive to make OpenRC stable then I suggest that I |
33 |
roll openrc-0.5.0 out sometime this week and try to roll rc events into |
34 |
0.6.0, the embedded stubs into 0.7.0 and we'll go from there. |
35 |
|
36 |
I know that Cardoe has been busy in RL of late and I've never pressed or |
37 |
been pressed into considering it stable. However, real bug reports and |
38 |
new feature implementations have slowed somewhat, so either it's Ready |
39 |
For Stable or no-ones using it. |
40 |
|
41 |
Thanks |
42 |
|
43 |
Roy |