1 |
Doug Goldstein wrote: |
2 |
> All, |
3 |
> |
4 |
> This is a formal notice to everyone that OpenRC will be hitting the |
5 |
> Gentoo tree sooner rather then later. I would like to see *ALL* arch |
6 |
> teams give the current code a whirl on their systems, which is |
7 |
> available via the layman module "openrc". |
8 |
> |
9 |
> I would also like to give the docs team a chance to weigh in here and |
10 |
> work with me on a migration guide as well as any necessary updates. |
11 |
> |
12 |
> That being said, I will be the primary point of contact on the |
13 |
> transition to OpenRC appearing in ~arch (along with it's associated |
14 |
> baselayout-2.0.0 ebuild). Any and all grievances, concerns, |
15 |
> suggestions and comments can and should be routed to me via the |
16 |
> associated Bugzilla entries or e-mail. |
17 |
> |
18 |
> I do not want OpenRC to come as a surprise to anyone and break their |
19 |
> system. I expect we will leave no stone unturned and go for a very |
20 |
> smooth transition. |
21 |
> |
22 |
> That being said, the bug for the addition of OpenRC is #212696 [1]. |
23 |
> The bug for the documentation is #213988 [2]. |
24 |
> |
25 |
> Lastly, I will be out of town March 21st through March 23rd. I will |
26 |
> not have IRC access but I will have e-mail and Bugzilla access. |
27 |
> |
28 |
> https://bugs.gentoo.org/show_bug.cgi?id=212696 |
29 |
> https://bugs.gentoo.org/show_bug.cgi?id=213988 |
30 |
> |
31 |
It appears my migration plan was not good enough for Mike Frysinger |
32 |
<vapier@g.o> and he went ahead and wrote his own version of the |
33 |
OpenRC ebuild, differing from the one in the OpenRC layman repo, and |
34 |
committed it to the tree this weekend. |
35 |
|
36 |
Since my offer to work on the migration was not good enough for him, I'm |
37 |
backing out and allowing him to handle the whole migration himself since |
38 |
I haven't heard from him at all despite Roy (author of OpenRC) and my |
39 |
attempts to contact him for 2 weeks regarding a migration plan for |
40 |
OpenRC. All issues and comments can be directed to him. |
41 |
|
42 |
I guess working together and documenting everything before having it hit |
43 |
the tree was a bad plan and it had to be one-upped. |
44 |
-- |
45 |
gentoo-dev@l.g.o mailing list |