Upload: bash-3.0-4 [test]
Tue Jul 5 17:55:00 GMT 2005
On Tue, 5 Jul 2005, Corinna Vinschen wrote:
> On Jul 5 13:32, Igor Pechtchanski wrote:
> > How about using a dummy executable that doesn't depend on anything and
> > does nothing but print out some pre-defined message, and copying that to
> > /bin/sh in the preremove script? That way, there will always be a
> > (non-working, but who cares) /bin/sh... I was going to suggest
> > /bin/false, but the new version actually depends on cygintl-3.dll and
> > cygiconv-2.dll -- go figure.
> Aren't we making this all too complicated? If you ask me, we should
> release a new setup.exe which refuses to deinstall the packages from the
> "Base" category. If anybody suffers from manual deinstalles, it's
> entirely a user fault and the person deserves all types of suffering.
It's not a question of deinstalling -- this also happens during upgrades.
We want to be able to upgrade /bin/sh cleanly. FWIW, I don't think it
matters that /bin/sh doesn't exist in the short time between removing the
old version and installing the new one, so a preremove approach is just
This doesn't invalidate your point about not allowing to uninstall stuff
in Base (at least, not without multiple warnings and "Are you sure?"s).
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
More information about the Cygwin-apps