From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21119 invoked by alias); 31 May 2010 23:43:59 -0000 Received: (qmail 21108 invoked by uid 22791); 31 May 2010 23:43:58 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from out5.smtp.messagingengine.com (HELO out5.smtp.messagingengine.com) (66.111.4.29) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 31 May 2010 23:43:55 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 59725F7A75 for ; Mon, 31 May 2010 19:43:53 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 31 May 2010 19:43:53 -0400 Received: from [192.168.1.3] (unknown [24.110.45.162]) by mail.messagingengine.com (Postfix) with ESMTPSA id F25EB5D206; Mon, 31 May 2010 19:43:52 -0400 (EDT) Message-ID: <4C04499D.7000002@cwilson.fastmail.fm> Date: Mon, 31 May 2010 23:43:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: Talk Amongst Yourselves Subject: Re: "TakeoffGW" References: <4C03BD54.4030801@cwilson.fastmail.fm> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2010-q2/txt/msg00044.txt.bz2 On 5/31/2010 2:25 PM, Andy Koppe wrote: > Seems it's just that listing that directory is blocked. Accessing > setup.ini within works fine, as does running setup.exe, although I > cancelled it while it was trying to download 65MBs worth of > msys-coreutils. Oh, that's hysterical. The previous version of msys-coreutils was built with i18n support via a statically linked version of libintl, because the then-current msys gcc was based on gcc-2.95.3, and Bruno's fancy-schmancy mechanism for avoiding auto-import didn't work with that old version. Hence, msys-libintl was static only. This meant that every single app in coreutils was 1.2MB or bigger, even /bin/true.exe. You wouldn't BELIEVE the howls of outrage. You'd think disk space was paid for in gold bricks, or something. Now, the msys project compressed all those tarballs using lzma, which has a 4MB dictionary -- so all that repeated code in each exe compressed VERY well. This guy repackaged using bz2, which doesn't (dictionary too small) -- even though the version of setup that he forked DOES support .lzma (and .xz) But the really funny bit is this: he's pointing at all the msys packages released prior to May 2010 -- AND the msys-gcc-3.4.4 compiler. Which means half of his libraries are circa gcc-2.x, and half are circa gcc-3.x. Given that there was an ABI change in the cygwin-based compilers between 2.x and 3.x (to support the C++ exceptions across DLLs, but it affected C code too) -- I'm thinking...FAIL. AND...he's also pointing at the "msysDVLPR" package, which will clobber/conflict with msys-gcc(3.4), msys-g++(3.4), msysCORE-dev, and msys-w32api... I happen to know about this because I spent the last several months, since msys-gcc-3.4.4 was released, updating all of the msys packages to that new compiler, and rolled them out over the last few weeks. (On the plus side, with the new msys-gcc, libintl CAN be built as a DLL, so all those msys-coreutils apps are back down to ~20k as they should be). Boy, this guy's running afoul of two different developer communities simultaneously, which don't normally agree. First there's the whole GPL setup.exe thing (plus we cygwinner's despair at yet another unsupported installation method for cygwin-derived stuff). Then, there's the massive expansion of many additional tools to the "msys" platform. The MSYS guys do NOT want to replace cygwin; they don't want to have an msys port of apache, or pidgen, or GNOME ... It's supposed to be a "Minimal SYStem" -- just barely enough posix support and tools to run configure scripts, with tweaks tuned for use with MinGW's gcc, rather than "cygwin's" gcc. Yeesh. And no, pier11 never mentioned these plans "over there", either. The really REALLY funny thing, is in just a few weeks, the MinGW folks are going to (finally) release an installer of their own, which is extensible and allows to "include by reference" other repositories of addons. Which means a lot of his "repackaging" work -- and setup.exe fork -- was totally unnecessary. -- Chuck