Mon May 19 23:34:00 GMT 2003
> > I could check for existance of a ksh symlink in the
> postinstall script
> > and create it if it's missing.
> That's precisely what you should do. All of this "create a symlink"
> talk is *specifically* about doing it in the postinstall
> script. That's
> the whole point.
OK, that's what I wanted to hear.
How should I deal with a symlink already present?
Are postinstall scripts allowed to be interactive (e.g. ask the user via
More information about the Cygwin-apps