From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC
Date: Wed, 11 Dec 2013 20:53:04 +0000 [thread overview]
Message-ID: <52A8D0B0.9010709@gentoo.org> (raw)
In-Reply-To: <52A8CF7D.3090309@gentoo.org>
On 12/11/2013 08:47 PM, Chris Reffett wrote:
> On 12/11/2013 3:41 PM, 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.
>>
>> 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? I know that once OpenRC with this change is
>> released, it will need to probably be p.masked until there is a new
>> release of sysvinit that updates the inittab.
>>
>> I'm not sure what else will break.
>>
>> Does anyone have any ideas wrt other things to look for, or should I
>> make the changes upstream and have people let us know what
>> else breaks?
>>
>> William
>>
>> [1] https://bugs.gentoo.org/show_bug.cgi?id=493958
> 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.
>
> Chris Reffett
>
>
+1
The ebuild can grep the inittab and it if finds an "rc" there, just
print a huge warning telling the user to migrate || die.
--
Regards,
Markos Chandras
next prev parent reply other threads:[~2013-12-11 20:53 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 [this message]
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
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=52A8D0B0.9010709@gentoo.org \
--to=hwoarang@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