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: Andy Moreton <andy DOT moreton AT artimi DOT com>, cygwin AT cygwin DOT com
Subject: Re: Bash 3.0 packaging problems
Date: Fri, 08 Jul 2005 15:41:15 +0000
Message-Id: <070820051541.11366.42CE9E9A000E9FA100002C6622058864420A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> 1) The info file is missing. Running "cygcheck -l bash" on bash 2.05 lists 
> "/usr/share/info/bash.info" but is not found in the bash 3.0 package.
> /usr/share/doc/Cygwin/bash-3.0.README suggest an info file should be 
> included.

Acknowledged.  I'll have to see why it disappeared, especially since
the original tarball includes it.  I'll also see about building the builtins.1
man page, and creating links for all builtins not also covered by
programs (ie. exit.1 would point to builtins.1, but false.1 is already
claimed by coreutils).

> 
> 2) The package scripts don't seem to remove /bin/bash as /bin/sh when 
>    downgrading to an older version. I would expect that either /bin/sh
>    would be be replaced with ash, or the new (downgraded) bash version.
>    - Run setup to upgrade to bash 3.0
>    - Run setup to downgrade bash back to 2.05:

It's a known problem that the bash preremove script is useless in
the current version of setup.exe (see
http://sources.redhat.com/ml/cygwin-apps/2005-07/msg00114.html).  As
to downgrading, you must also downgrade the ash package to get
/bin/sh to be ash again via setup.exe.  Or, just hand-copy /bin/ash.exe
from the new ash over /bin/sh.exe (of course, you have to do this from
bash or from Windows explorer, and not from sh, since you can't overwrite
a running executable).

--
Eric Blake
volunteer cygwin bash maintainer



--
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/