This is the mail archive of the
mailing list for the Cygwin project.
Re: NOTICE for all package maintainers with faulty post-install scripts
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 12 Aug 2010 09:56:49 -0400
- Subject: Re: NOTICE for all package maintainers with faulty post-install scripts
- References: <20100811231554.GA4437@ednor.casa.cgf.cx>
> Thanks to Jon Turney's recent patch we've discovered that many
> post-install packages were previously failing silently.
Failing silently... so what is the preferred protocol in case a
post-install script fails? Emit a message to stderr, which will be caught
and shown to the user?
If a post-install script fails in an ignorable way, then does this mean
it's not acceptable to allow the script to exit with a non-zero status?
That is, we have to either exit 0, or else exit non-zero and emit a useful
If a post-install script succeeds (and exits with status 0) but still emits
text to stderr or even stdout, will that text also be caught and shown to
Do the answers to all of the above also apply to preremove scripts?
Sorry if some of this has already been discussed. I haven't followed all
of the discussion of this new feature.