Upload: bash-3.0-4 [test]
Tue Jul 5 17:24:00 GMT 2005
On Jul 5 12:33, Igor Pechtchanski wrote:
> This isn't good enough -- I think you do need a preremove script. I've
> been trying to figure out why the no-preremove solution seems wrong, and
> came up with the following scenario: suppose bash is linked against an
> older libreadline, and the user upgrades both bash and libreadline to
> newer versions. /bin/sh will be a copy of the old version of bash, but
> after the upgrade it won't have the necessary DLLs. So, running the
> postinstall script (with "/bin/sh --version") will result in a "Can't
> locate DLL" popup, which should be a no-no in a postinstall script.
Actually that would be covered by postinstall scripts which don't use
/bin/sh at all. What about using md5sum to figure out if it's bash
or ash and if it's an old or new version? I still don't like the idea
of a preremove script removing /bin/sh under whatever circumstances.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:firstname.lastname@example.org
Red Hat, Inc.
More information about the Cygwin-apps