public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] baselayout --> openrc ?
Date: Sat, 23 Oct 2010 02:48:58 +0200	[thread overview]
Message-ID: <201010230248.58751.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20101022215049.GE2294@Caemlyn>

Apparently, though unproven, at 23:50 on Friday 22 October 2010, Zeerak 
Mustafa Waseem did opine thusly:

> > It's openrc-${PV}+1 - there's no question about that.
> >
> > 
> >
> > Until someone actually ponies up and commits something other than openrc
> > to  the tree, it's gonna stay on openrc.
> >
> > 
> >
> > I think you misunderstand what ~arch means.
> 
> I'll gladly be explained, just in case I should have it wrong. :-)
> 
> What I meant however was that there has been talk of starting a migration
> of ~arch users to devicekit when it is deemed ready. As far as I remember
> no conclusion was brought to that discussion other than openrc being moved
> inhouse and seeing how that went. So the ball is still in the air as far
> as openrc and a replacement goes, to my understanding.


~arch is the collection of unstable ebuilds in portage; stuff that is good 
enough for a release but not yet fully tested within a Gentoo system. With 
enough successful feedback from users, it is marked stable and moves to 
"arch".

~arch is not experimental, stuff planned for the future, someone's wicked 
overlay or anything else other than stable releases in a *gentoo* test phase, 
i.e. it's not so much the software that's being tested but the ebuild.

devicekit stands very little chance of ever being the default. It depends on 
dbus and expat. Remember hal and all the crap that came along with it? Gentoo 
is not Ubuntu or Fedora, it is installable on anything from ARM phones to 
IBM's gigantic hard iron. Why on earth would anyone mandate dbus to be 
compulsory on a headless server for example?

If you want to know what the future holds for Gentoo, best not to listen much 
to a bunch of dudes rambling on gentoo-dev and blogs. They're just talking, 
and talk is cheap. If you want to know what the future holds for @system and 
the toolchain, vapier is a good one to listen to. So's the council, GLEPs and 
whatever happens in voting. The kong thread that's been mentioned in this 
thread has a gem of a quote from vapier, something like:

"People saw Roy moving away from Gentoo, and freaked out."

That's it, nothing more. Some dudes freaked out.

Besides, lookee here:

nazgul ~ # eix -e devicekit
* sys-apps/devicekit
     Available versions:  (~)003 {doc}
     Homepage:            http://www.freedesktop.org/wiki/Software/DeviceKit
     Description:         D-Bus abstraction for enumerating devices and 
listening for device events using udev

nazgul ~ # eix -e dbus-glib
[I] dev-libs/dbus-glib
     Available versions:  0.86 (~)0.88 {bash-completion debug doc static-libs 
test}
     Installed versions:  0.88(00:25:33 12/10/10)(bash-completion -debug -doc 
-static-libs -test)
     Homepage:            http://dbus.freedesktop.org/
     Description:         D-Bus bindings for glib

nazgul ~ # eix systemd
No matches found.

devicekit has one version (003) and systemd doesn't even have an ebuild in the 
tree. That system is probably sitting about where openrc was when Roy had 
gotten to 20% of where he eventually took it.

openrc works, it has three outstanding edge case blocker bugs. What possible 
technical reason is there to go chasing butterflies down some totally unproven 
path?

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-10-23  0:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  2:02 [gentoo-user] baselayout --> openrc ? James
2010-10-22  2:18 ` Beau Henderson
2010-10-22 10:13 ` Michael Hampicke
2010-10-22 11:18   ` David Relson
2010-10-22 11:29     ` Neil Bothwick
2010-10-22 16:19       ` Stroller
2010-10-22 19:54         ` Neil Bothwick
2010-10-22 20:37           ` Zeerak Mustafa Waseem
2010-10-22 20:59             ` Alan McKinnon
2010-10-22 21:50               ` Zeerak Mustafa Waseem
2010-10-23  0:48                 ` Alan McKinnon [this message]
2010-10-23 10:57                   ` Zeerak Mustafa Waseem
2010-10-22 20:32         ` Alan McKinnon
2010-10-22 20:52           ` Dale
2010-10-22 21:02             ` Alan McKinnon
2010-10-26 13:39               ` Dean Matzkov
2010-10-26 14:42                 ` Alan McKinnon
2010-10-22 22:13             ` Neil Bothwick
2010-10-22 22:26               ` Dale
2010-10-23  0:53                 ` Alan McKinnon
2010-10-23  0:50               ` Alan McKinnon
     [not found]                 ` <20101023100333.221a888d@digimed.co.uk>
2010-10-23  9:23                   ` Dale
2010-10-24 14:30                   ` Mike Edenfield
2010-10-24 15:45                     ` Neil Bothwick
2010-10-24 17:07                     ` Albert Hopkins
2010-10-24 22:29                     ` Alan McKinnon
2010-10-25  0:11                       ` Neil Bothwick
2010-10-25 14:18                         ` BRM
2010-10-25 14:29                           ` Neil Bothwick
2010-10-23  9:43             ` Peter Humphrey
2010-10-22 22:43           ` Stroller
2010-10-23  1:04             ` Alan McKinnon
2010-10-22 17:13       ` [gentoo-user] Re: baselayout --&gt; " James
2010-10-22 15:06   ` [gentoo-user] baselayout --> " Paul Hartman
2010-10-22 20:12     ` Stefan G. Weichinger
2010-10-23 11:43 ` daid kahl

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=201010230248.58751.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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