1 |
Apparently, though unproven, at 23:50 on Friday 22 October 2010, Zeerak |
2 |
Mustafa Waseem did opine thusly: |
3 |
|
4 |
> > It's openrc-${PV}+1 - there's no question about that. |
5 |
> > |
6 |
> > |
7 |
> > |
8 |
> > Until someone actually ponies up and commits something other than openrc |
9 |
> > to the tree, it's gonna stay on openrc. |
10 |
> > |
11 |
> > |
12 |
> > |
13 |
> > I think you misunderstand what ~arch means. |
14 |
> |
15 |
> I'll gladly be explained, just in case I should have it wrong. :-) |
16 |
> |
17 |
> What I meant however was that there has been talk of starting a migration |
18 |
> of ~arch users to devicekit when it is deemed ready. As far as I remember |
19 |
> no conclusion was brought to that discussion other than openrc being moved |
20 |
> inhouse and seeing how that went. So the ball is still in the air as far |
21 |
> as openrc and a replacement goes, to my understanding. |
22 |
|
23 |
|
24 |
~arch is the collection of unstable ebuilds in portage; stuff that is good |
25 |
enough for a release but not yet fully tested within a Gentoo system. With |
26 |
enough successful feedback from users, it is marked stable and moves to |
27 |
"arch". |
28 |
|
29 |
~arch is not experimental, stuff planned for the future, someone's wicked |
30 |
overlay or anything else other than stable releases in a *gentoo* test phase, |
31 |
i.e. it's not so much the software that's being tested but the ebuild. |
32 |
|
33 |
devicekit stands very little chance of ever being the default. It depends on |
34 |
dbus and expat. Remember hal and all the crap that came along with it? Gentoo |
35 |
is not Ubuntu or Fedora, it is installable on anything from ARM phones to |
36 |
IBM's gigantic hard iron. Why on earth would anyone mandate dbus to be |
37 |
compulsory on a headless server for example? |
38 |
|
39 |
If you want to know what the future holds for Gentoo, best not to listen much |
40 |
to a bunch of dudes rambling on gentoo-dev and blogs. They're just talking, |
41 |
and talk is cheap. If you want to know what the future holds for @system and |
42 |
the toolchain, vapier is a good one to listen to. So's the council, GLEPs and |
43 |
whatever happens in voting. The kong thread that's been mentioned in this |
44 |
thread has a gem of a quote from vapier, something like: |
45 |
|
46 |
"People saw Roy moving away from Gentoo, and freaked out." |
47 |
|
48 |
That's it, nothing more. Some dudes freaked out. |
49 |
|
50 |
Besides, lookee here: |
51 |
|
52 |
nazgul ~ # eix -e devicekit |
53 |
* sys-apps/devicekit |
54 |
Available versions: (~)003 {doc} |
55 |
Homepage: http://www.freedesktop.org/wiki/Software/DeviceKit |
56 |
Description: D-Bus abstraction for enumerating devices and |
57 |
listening for device events using udev |
58 |
|
59 |
nazgul ~ # eix -e dbus-glib |
60 |
[I] dev-libs/dbus-glib |
61 |
Available versions: 0.86 (~)0.88 {bash-completion debug doc static-libs |
62 |
test} |
63 |
Installed versions: 0.88(00:25:33 12/10/10)(bash-completion -debug -doc |
64 |
-static-libs -test) |
65 |
Homepage: http://dbus.freedesktop.org/ |
66 |
Description: D-Bus bindings for glib |
67 |
|
68 |
nazgul ~ # eix systemd |
69 |
No matches found. |
70 |
|
71 |
devicekit has one version (003) and systemd doesn't even have an ebuild in the |
72 |
tree. That system is probably sitting about where openrc was when Roy had |
73 |
gotten to 20% of where he eventually took it. |
74 |
|
75 |
openrc works, it has three outstanding edge case blocker bugs. What possible |
76 |
technical reason is there to go chasing butterflies down some totally unproven |
77 |
path? |
78 |
|
79 |
-- |
80 |
alan dot mckinnon at gmail dot com |