Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 15 Oct 2002 19:39:38 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Errors during setup post-install scripts Message-ID: <20021015233938.GA17874@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3DAC84A2 DOT 7020306 AT cox DOT net> <008801c274a0$e308f680$78d96f83 AT bowsher DOT foo> <1034724782 DOT 22361 DOT 34 DOT camel AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1034724782.22361.34.camel@lifelesswks> User-Agent: Mutt/1.4i On Wed, Oct 16, 2002 at 09:33:02AM +1000, Robert Collins wrote: >On Wed, 2002-10-16 at 09:11, Max Bowsher wrote: >> 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. > >It's been discussed in the cygwin-apps list, at length. > >> 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.) > >IIRC someone offered to do one at one point, and nothing came of it. I'm >not for or against a setup.exe web todo list, as long as: >1) I don't need to maintain/review/care about it. >2) It gets syncronised with the CVS TODO list. I have the same two concerns. My experience with the cygwin DLL to-do list has been primarily negative so I don't want to be involved in something else like this. -- 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/