public inbox for
 help / color / mirror / Atom feed
From: Charles Wilson <>
To: Talk Amongst Yourselves <>
Subject: Re: "TakeoffGW"
Date: Mon, 31 May 2010 23:43:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

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.


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.


      reply	other threads:[~2010-05-31 23:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 12:43 "TakeoffGW" Andy Koppe
2010-05-31 13:45 ` "TakeoffGW" Charles Wilson
2010-05-31 17:02   ` "TakeoffGW" Christopher Faylor
2010-05-31 18:25   ` "TakeoffGW" Andy Koppe
2010-05-31 23:43     ` Charles Wilson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).