From: Paul Tagliamonte <paultag@debian.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC
Date: Wed, 11 Dec 2013 15:56:13 -0500 [thread overview]
Message-ID: <20131211205613.GA16261@leliel.pault.ag> (raw)
In-Reply-To: <52A8CF7D.3090309@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
[I'm not the OpenRC maintainer, I'm only on gentoo-devel because I'm
generally interested, and I saw this, I'm not speaking for zigo or
anything here.]
On Wed, Dec 11, 2013 at 03:47:57PM -0500, Chris Reffett 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.
>
> Chris Reffett
Hi, Gentoo (and hello world),
I'm breaking my streak of lurking to comment generally on the Debian
procedure here.
I'm sure the Debian folks would be happy to strip the symlink from the
deb over having to patch OpenRC's rc binary => openrc against the
upstream source.
Shipping /usr/bin/rc => /usr/bin/openrc would be totally cool for
Debian, I believe. Hopefully the OpenRC team will come in and correct me
if I'm wrong :)
Fondly,
Paul
--
.''`. Paul Tagliamonte <paultag@debian.org> | Proud Debian Developer
: :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87
`. `'` http://people.debian.org/~paultag
`- http://people.debian.org/~paultag/conduct-statement.txt
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-11 20:56 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 ` Paul Tagliamonte [this message]
2013-12-11 21:09 ` [gentoo-dev] " 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=20131211205613.GA16261@leliel.pault.ag \
--to=paultag@debian.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