From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC
Date: Wed, 11 Dec 2013 19:38:29 -0600 [thread overview]
Message-ID: <CAFWqQMRnhO_ijF9vXTZ=JE2evk7QaJxXdJKWCe7x3KzUBKAarQ@mail.gmail.com> (raw)
In-Reply-To: <52A9052E.50301@gentoo.org>
On Wed, Dec 11, 2013 at 6:37 PM, Patrick Lauer <patrick@gentoo.org> wrote:
> On 12/12/2013 04:41 AM, William Hubbs wrote:
>> All,
>>
>> We got a request from Debian to rename the "rc" binary of OpenRC due to
>> a naming conflict they have. They have a port of the at&t plan 9 shell,
>> which has a binary named "rc" as well[1].
>>
>> My thought is to rename our "rc" to "openrc", since that would be
>> unique.
>
> Make it build-time configurable. Keep default at "rc". Let Debian and
> others rename it as they want/need.
>
>> I know at least one thing that will break is everyone's inittab, so
>> should I sed their inittab in our live ebuild or expect them to fix it
>> and give a warning?
>
> It's change to change things, it doesn't fix any bugs we have.
>
> So don't break things for fun, please ...
Honestly, with Linux systems a symlink won't matter. Just rename the
binary to "openrc" so that we are closer with Debian. It would be nice
if in the future docs and blogs and other things could share the same
info.
For Gentoo just symlink rc -> openrc and call it a day. There's also
no reason to remove the symlink in the next release like others have
said. Keep the thing around for as long as is possible. Cause if you
drop it, you're liable to break someone upgrading an old system and
they have a higher chance to miss an important ewarn and you know how
much I hate breaking upgrades.
--
Doug Goldstein
next prev parent reply other threads:[~2013-12-12 1:38 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
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 [this message]
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='CAFWqQMRnhO_ijF9vXTZ=JE2evk7QaJxXdJKWCe7x3KzUBKAarQ@mail.gmail.com' \
--to=cardoe@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