This is the mail archive of the
mailing list for the Cygwin project.
RE: cygcheck improvements
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Dave Korn <dave dot korn at artimi dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 2 Nov 2005 13:03:19 -0500 (EST)
- Subject: RE: cygcheck improvements
- References: <SERRANOwAeRaNgEpTX5000000cf@SERRANO.CAM.ARTIMI.COM>
- Reply-to: cygwin at cygwin dot com
On Wed, 2 Nov 2005, Dave Korn wrote:
> Christopher Faylor wrote:
> > On Wed, Nov 02, 2005 at 05:37:25PM -0000, Dave Korn wrote:
> >> Christopher Faylor wrote:
> >>> What other kind of common things could cygcheck be testing for?
> Hey, I had another idea. It should definitely scan /etc/postinstall
> and report any scripts that failed to complete (i.e. don't end with
Sigh, this would imply that (a) postinstall scripts produce valuable exit
codes (or are run with "set -e", so that they bail out at first sign of
trouble), and that (b) setup doesn't rename scripts that didn't complete
normally to "*.done". Neither is true at the moment. PTC, of course.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html