public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC
Date: Wed, 11 Dec 2013 16:28:36 -0500	[thread overview]
Message-ID: <CAGfcS_nUKsjOTUic+x_SV4s9_H+S+vHkzqnJosZuXxhWZcX5dg@mail.gmail.com> (raw)
In-Reply-To: <52A8CF7D.3090309@gentoo.org>

On Wed, Dec 11, 2013 at 3:47 PM, Chris Reffett <creffett@gentoo.org> wrote:
> The idea of running a sed on inittab in an ebuild, no matter what the
> context, terrifies me. Perhaps we can ease this in slowly by renaming rc ->
> openrc and symlinking rc -> openrc and making a release with that change
> concurrent with a news item? Or even just do that in the ebuild rather than
> in the actual sources. I don't think Debian will keel over and die if it
> takes a little extra time for the change to go through, and it beats a ton
> of broken systems.

++

No reason the symlink couldn't be done in the ebuild either - which
keeps the package itself clean.  There could be news to clean up
inittab and such, and then perhaps down the road the compat symlink
could be removed.

Nice to see interest in Debian (granted, I know there was interest
quite a while back).  Having more and better options is just good for
everybody - I'd like to see OpenRC become the best traditional-style
service manager around (though honestly I'd be hard-pressed to think
of any that are quite as good already).

I think one thing that would be nice to dream about someday would be a
systemd-compatibility init.d script.  That would be symlinked to a
service name just like a typical network interface script, and would
look for a unit file and interpret it (perhaps just taking a path from
conf.d).  I'd think it wouldn't be hard to do, setting aside the more
active-management features of systemd.

Rich


  parent reply	other threads:[~2013-12-11 21:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 20:41 [gentoo-dev] rfc: renaming "rc" binary in OpenRC William Hubbs
2013-12-11 20:47 ` Alon Bar-Lev
2013-12-11 21:04   ` William Hubbs
2013-12-11 20:47 ` Chris Reffett
2013-12-11 20:53   ` Markos Chandras
2013-12-11 21:28     ` [gentoo-dev] " Duncan
2013-12-11 22:46       ` William Hubbs
2013-12-11 20:56   ` [gentoo-dev] " Paul Tagliamonte
2013-12-11 21:09     ` Markos Chandras
2013-12-11 21:14       ` Paul Tagliamonte
2013-12-11 22:50       ` William Hubbs
2013-12-11 21:28   ` Rich Freeman [this message]
2013-12-12  0:41     ` Patrick Lauer
2013-12-12  8:26       ` [gentoo-dev] " Martin Vaeth
2013-12-12 12:56       ` [gentoo-dev] " Rich Freeman
2013-12-12  0:37 ` Patrick Lauer
2013-12-12  1:38   ` Doug Goldstein
2013-12-12  7:41 ` Samuli Suominen
2013-12-12 15:15   ` William Hubbs
2013-12-12 15:46 ` Alexander Berntsen
2013-12-13 12:31   ` Samuli Suominen
2013-12-13 13:31     ` Alexander Berntsen
2013-12-13 15:59   ` Mike Gilbert
2013-12-13 17:23     ` William Hubbs
2013-12-13 19:53       ` [gentoo-dev] " Duncan
2013-12-13 22:03         ` William Hubbs
2013-12-14 12:47           ` Duncan

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=CAGfcS_nUKsjOTUic+x_SV4s9_H+S+vHkzqnJosZuXxhWZcX5dg@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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