> "Paul; 2005 January 30 Sunday 18:24
>> clearly do a better job explaining in the first place. With all due
>> respect, I find the grid horribly confusing and aesthetically
>> displeasing to boot. From what I gather from the page, it's
> I also find it confusing. The best I can make out, you download the
Thanks for the "me too", at least I know I'm not the only one. Getting
beyond that, if there's any way I can help, I'll give it a shot. I can
set up my own Apache and play with server side includes and redesign the
table structure, if that's the path of least resistance at this point.
I can reword the page also, if that would be of help. First I have to
be sure that I know what I'm doing, and have an idea of where the
project is going, with the big files vs little files approach. I would
use less words, but briefly describe what each download contains, why
you would need it, and if it is included in a larger download (and the
versions/dates of the source or binaries and of the build).
> latest mingw/msys, and then all the appropriate 'current' packages
> that have a newer date than the mingw package you just installed. I
> wonder, is that correct? I'm also not sure what order i'm supposed
> to extract them, or if it makes a difference. I suppose I should've
> done it in date-order too....
Well I did this, figuring "the big file has more stuff in it", for lack
of a proper MANIFEST, but some stuff is missing apparently. I even sat
and tried to add up the file sizes. All the little files together are
much bigger than the big 50MB MinGW rc-# file, so I would likely need
something of the smaller files? I know roughly what a gcc-lang or
binutils includes, in Linux, and can only guess it's about the same for
MinGW/MSYS. But I have no idea what's in the MinGW or msysDTK files,
for instance. Unless of course I download and install and look, but
that's after the fact.