This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Upload: bash-3.0-5 [ready!]
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 6 Jul 2005 15:29:09 +0200
- Subject: Re: Upload: bash-3.0-5 [ready!]
- References: <42CBD8B0.4010200@byu.net>
- Reply-to: cygwin-apps at cygwin dot com
On Jul 6 07:12, Eric Blake wrote:
> I think this version is ready for primetime, so my setup.hint no longer
> mentions a test version. You can delete 2.05b-16, and 3.0-[34], leaving
> 2.05b-17 as previous and 3.0-5 as current. The following need to be done
> with ash, then both packages uploaded simultaneously for minimum confusion
> (although the postinstalls should ensure a success path regardless of
> which one is done first in isolation):
> + repackage /bin/sh.exe as /bin/ash.exe
> + remove /usr/share/man/man1/ash.1 from the package
^^^^^
you meant sh.1, don't you?
> + add a dependency to bash in setup.hint (needed to ensure bash is
> installed to provide /bin/sh for all other packages that depended on ash
> providing /bin/sh)
> + add /etc/postinstall/00ash.sh:
>
> #!/bin/ash
> # Ash postinstall script. This ensures that /bin/sh exists and is
> # runnable, favoring bash, and updating only if it is missing or ash
>
> update=no
> # Is /bin/sh missing, or have broken dependencies?
> case `(cygcheck /bin/sh.exe) 2>&1` in
> *Error:\ could\ not\ find*) update=yes ;;
> *) # We can run it. Is the version from ash?
> case `(/bin/sh.exe --version) 2>&1` in
> Illegal\ option\ --*) update=yes ;;
> esac ;;
> esac
> # Update, if needed, with hard link on supporting platforms.
> if test $update = yes ; then
> ln -f /bin/bash.exe /bin/sh.exe || ln -f /bin/ash.exe /bin/sh.exe
^^^^^ ^^^^^
Did you read my posting from 6 hours ago?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.