public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC
Date: Fri, 13 Dec 2013 10:59:35 -0500	[thread overview]
Message-ID: <CAJ0EP43QmB3pBZM_GCXLyVL_Bs7xp_Vm14CodGrJHCUGA7sT7Q@mail.gmail.com> (raw)
In-Reply-To: <52A9DA57.6070700@plaimi.net>

On Thu, Dec 12, 2013 at 10:46 AM, Alexander Berntsen
<alexander@plaimi.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 11/12/13 21:41, William Hubbs wrote:
>> My thought is to rename our "rc" to "openrc", since that would be
>> unique.
> orc is shorter and more punny (nice excuse for designing an orcish cow
> mascot).
>
> On 11/12/13 22:04, William Hubbs wrote:> On Wed, Dec 11, 2013 at
> 10:47:49PM +0200, Alon Bar-Lev wrote:
>>> are you going to rename also rc-service and rc-update?
>>
>> No, there isn't a need for that, just "rc".
> Please rename all of them, to provide uniform naming. This way, typing
> orc, and tab-tabing in BASH will give you a list of orc-related
> executables, just like with rc now.
>

That makes no sense; there is almost no reason to manually invoke the
"rc" binary currently, an Gentoo users are already familiar with names
like "rc-update" and "service".

Renaming everything just forces users to learn new command names for no reason.


  parent reply	other threads:[~2013-12-13 15:59 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
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 [this message]
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=CAJ0EP43QmB3pBZM_GCXLyVL_Bs7xp_Vm14CodGrJHCUGA7sT7Q@mail.gmail.com \
    --to=floppym@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