public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jonathan Callen <jcallen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: newsitem: OpenRC runscript transition (draft 2)
Date: Mon, 22 Aug 2016 20:56:49 -0400	[thread overview]
Message-ID: <3b4fbcd2-d697-5e6a-c0d5-d2d272f262ee@gentoo.org> (raw)
In-Reply-To: <20160822214525.GA18116@whubbs1.gaikai.biz>


[-- Attachment #1.1: Type: text/plain, Size: 1017 bytes --]

On 08/22/2016 05:45 PM, William Hubbs wrote:
> On Mon, Aug 22, 2016 at 09:53:48PM +0200, Ulrich Mueller wrote:
>>>>>>> On Mon, 22 Aug 2016, William Hubbs wrote:
>>
>>> Display-If-Installed: <sys-apps/openrc-0.22
>>
>> Why the condition on the version number?
> 
> I suppose I could change this to just sys-apps/openrc
> 
>>
>>> # emerge --oneshot -av $(grep -l "#!/sbin/runscript" /etc/init.d/*)
>>
>> Hm, I think you'll want single quotes there, otherwise the exclamation
>> mark could trigger bash history expansion. Alternatively, grep for
>> /sbin/runscript without the shebang (with the additional advantage
>> that it would also catch cases with whitespace after the #!).
> 
> Is '#! /sbin/runscript' a valid shebang line? I didn't think you could
> have whitespace after the '#!'.
> 
> William
> 

Yes, it is.  I just checked my /usr/bin, and found over 100 scripts that
all begin with the string "#! /", including many scripts from autoconf,
among others.

-- 
Jonathan Callen


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 847 bytes --]

      reply	other threads:[~2016-08-23  0:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 19:03 [gentoo-dev] newsitem: OpenRC runscript transition (draft 2) William Hubbs
2016-08-22 19:52 ` Pacho Ramos
2016-08-22 19:53 ` Ulrich Mueller
2016-08-22 21:45   ` William Hubbs
2016-08-23  0:56     ` Jonathan Callen [this message]

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=3b4fbcd2-d697-5e6a-c0d5-d2d272f262ee@gentoo.org \
    --to=jcallen@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