Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: ericblake AT comcast DOT net (Eric Blake)
To: Shankar Unni <shankarunni AT netscape DOT net>, cygwin AT cygwin DOT com
Subject: Re: How do I make /bin/sh=sh
Date: Mon, 22 Aug 2005 20:40:06 +0000
Message-Id: <082220052040.28314.430A38260007178400006E9A22058861720A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> > Actually, I'm playing with a change to bash, soon to be bash-3.0-12,
> > where the postinstall script will leave /bin/sh alone if its timestamp
> > is newer than /bin/bash.  
> 
> For one release. What happens after the next upgrade to bash?

My plan for bash-3.0-12 and beyond is to only upgrade /bin/sh to the
newest bash version if /bin/sh has an older timestamp than /bin/bash,
and is not ksh or zsh.  So, using 'touch -d "+2 years" /bin/sh.exe'
would exempt /bin/sh from updates for the next two years, no matter
how often bash upgrades occur in the meantime, and no matter if
/bin/sh is ash because you wanted it that way (at the expense of
having a file modified 2 years in the future!  Isn't time travel fun? :)

--
Eric Blake



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