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 To: cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Charles Wilson Newsgroups: gmane.os.cygwin Subject: Re: Fascinating setup issues (?) Date: Wed, 22 May 2002 18:17:18 -0400 Lines: 44 Message-ID: <3CEC18EE.5000602@ece.gatech.edu> References: <004b01c201d6$05cd87a0$6132bc3e AT BABEL> NNTP-Posting-Host: midbrain.ibb.gatech.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1022105804 21089 128.61.133.204 (22 May 2002 22:16:44 GMT) X-Complaints-To: usenet AT main DOT gmane DOT org NNTP-Posting-Date: Wed, 22 May 2002 22:16:44 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us Conrad Scott wrote: > (*) The gdbm and readline packages should (but don't) require texinfo in > setup.ini, since both of these packages call install-info in their > postinstall scripts. Since both these packages are in the default download > set, and texinfo isn't, the postinstall phase of the default download (quite > silently) fails. Noted. Will fix. > There are several other packages that also call install-info in their > postinstall scripts and which don't require texinfo in setup.ini: > autoconf-devel, automake-devel, bzip2, enscript, gettext, gnugo, gsl, > indent, libtool-devel, nano, tetex, wget. autoconf-devel, automake-devel, bzip2, gettext, libtool-devel: Noted. Will fix. > (*) Altho' I said I wasn't going to mention any bugs in setup.exe (and I'm > NOT going to mention the repeated blue screens of death it's giving me on > w2k), Since you didn't mention it, I won't mention that I get those too. And I won't mention that *EVERY* time I disassemble the crashdump, it's *ALWAYS* the fault of McAfee. Nope, not gonna mention that. > (*) And I WON'T mention the THREE blue screens I've had from setup.exe. So > that's not a problem :-) (or, at least, not a problem for anyone but Mr > Gates, I assume.) And I won't mention that the blame goes to Network Associates...and not Bill, in this case. --Chuck -- 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/