Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <008801c274a0$e308f680$78d96f83@bowsher.foo>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "David A. Cobb" <superbiskit AT cox DOT net>,
   "Cygwin Discussion" <cygwin AT cygwin DOT com>
References: <3DAC84A2 DOT 7020306 AT cox DOT net>
Subject: Re: Errors during setup post-install scripts
Date: Wed, 16 Oct 2002 00:11:11 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

David A. Cobb wrote:
> Would it be a big deal to have the various setup scripts send their
> output to, say, /var/log/setup/SCRIPTNAME.log?

Probably not, but someone has to actually do it.

Perhaps we should have a setup.exe web-based todo list? Like the current one
for the DLL?
(I know there is a text file in CVS, but web would allow people to submit
items.)

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/