public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1
Date: Sat, 25 Feb 2017 16:46:00 -0000	[thread overview]
Message-ID: <ed828046-15d2-6cbe-4e48-c3d72839572e@gmail.com> (raw)
In-Reply-To: <58af3c19.01309d0a.781cc.afce@mx.google.com>

On 2/23/2017 2:46 PM, Steven Penny wrote:
> On Thu, 23 Feb 2017 20:38:08, Andrey Repin wrote:
>> $ cat /etc/postinstall/zp_dash-as-bin-sh.dash
>> #!/bin/dash
> 
>> test ! -h /bin/sh.exe && {
>>   _f="$(mktemp /bin/sh.XXXXXX)"
>>   {
>>     mv /bin/sh.exe "$_f"
>>     ln -s /bin/dash.exe /bin/sh.exe
>>   } || mv "$_f" /bin/sh.exe
>>   rm "$_f"
>> }
>> exit 0
> 
> This is a bad idea.
> 
> If script succeeds, then yes sh is now a symlink to Dash, but only for my
> system. I still have to use #!/bin/dash with my scripts, because otherwise
> people with Bash -> sh will not get the speed boost. The whole point of
> this
> thread is that it should be changed for everyone.

If *your* script has a dependency to run using *dash* instead of *sh*
then you _must_ use #!/bin/dash anyway.  And what I _*I*_ don't want
dash as /bin/sh?  You see not everyone in the community will agree.  You
can make the suggestion to those using your script to do so otherwise
but forcing dash as /bin/sh worldwide isn't something you can actually do.

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2017-02-25 16:46 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 14:01 Eric Blake (cygwin)
2017-02-23  4:20 ` Steven Penny
2017-02-23 17:50   ` Andrey Repin
2017-02-23 19:46     ` Steven Penny
2017-02-23 19:59       ` Brian Inglis
2017-02-23 20:41         ` Eric Blake
2017-02-24  7:19           ` Yaakov Selkowitz
2017-02-23 23:44         ` Steven Penny
2017-02-24 14:32           ` Eric Blake
2017-02-24 19:19             ` Brian Inglis
2017-02-23 22:05       ` Andrey Repin
2017-02-23 23:01         ` Tony Kelman
2017-02-23 23:04           ` Eliot Moss
2017-02-23 23:12             ` Kenneth Wolcott
2017-02-23 23:30             ` Vince Rice
2017-02-23 23:35           ` Andrey Repin
2017-02-24  3:16           ` Larry Hall (Cygwin)
2017-02-24  3:18           ` Larry Hall (Cygwin)
2017-02-24  4:57             ` Steven Penny
2017-02-24 14:43               ` Eric Blake
2017-02-24 15:05                 ` Lee Dilkie
2017-02-25 16:55                 ` Steven Penny
2017-03-01 23:57                   ` Matt Seitz (matseitz)
2017-02-23 23:33         ` Steven Penny
2017-02-25 16:46       ` cyg Simple [this message]
2017-02-25 17:09         ` Steven Penny
2017-02-27 10:20           ` Csaba Raduly
2017-02-27 12:48             ` Steven Penny
2017-02-27 23:13           ` Duncan Roe
2017-02-28  0:51             ` Steven Penny
2017-02-28 20:52               ` cyg Simple
2017-02-28 21:43                 ` Steven Penny
2017-03-01 14:42                   ` cyg Simple
2017-03-02  0:22                     ` Steven Penny
2017-03-02  3:46                       ` Vince Rice
2017-03-02  5:27                         ` Steven Penny
2017-03-02  5:31                           ` Vince Rice
2017-03-02 12:36                             ` Steven Penny
2017-03-02 13:37                               ` Marco Atzeri
2017-03-02 14:29                                 ` Eric Blake
2017-03-02 16:16                                   ` Nellis, Kenneth (Conduent)
2017-03-02 17:28                                   ` Brian Inglis
2017-03-02 18:45                                     ` Eric Blake
2017-03-02 23:23                                       ` Brian Inglis
2017-03-02 18:28                                   ` Achim Gratz
2017-03-02 14:31                                 ` Brian Inglis

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=ed828046-15d2-6cbe-4e48-c3d72839572e@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).