From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin-talk@cygwin.com
Subject: Re: "TakeoffGW"
Date: Mon, 31 May 2010 13:45:00 -0000 [thread overview]
Message-ID: <4C03BD54.4030801@cwilson.fastmail.fm> (raw)
In-Reply-To: <AANLkTinwsZpZO4Vt2gwuAnxOGKFaXdAPPh05dIYn38qd@mail.gmail.com>
On 5/31/2010 8:43 AM, Andy Koppe wrote:
> Yay, another Cygwin 1.3.3 (aka MSYS) distribution, this time using
> Cygwin's latest setup.exe:
>
> http://sourceforge.net/projects/takeoffgw
So far, it's only a fork of setup.exe. It doesn't actually include any
installable components. Looking at the patches, the "mirror.lst" points to:
http://takeoffgw.sourceforge.net/R0/ -- which doesn't exist, and
ftp://localhost/takeoffgw/
I think "pier11" neglected to test his new brainchild on a different
computer...
The fun part is, he forked the cygwin-1.7 version of setup.exe. I have
a hunch that our latest setup.exe does a lot of NTSEC things that might
not actually play very well with cygwin-1.3.3/MSYS.
In any case, I think this is more a concern for the MinGW/MSYS fellas:
"Accompanying files (setup.hint) contain reference to original binary
packages on MinGW site: https://sourceforge.net/projects/mingw/files/"
In otherwords, if he ever actually uploads the setup.ini, it'll point to
the mingw project's tarballs (for MinGW gcc, MSYS components, etc).
'Course, they don't ptovide any md5sum signatures, so I kinda wonder
what this new setup.exe fork will think about that...
--
Chuck
next prev parent reply other threads:[~2010-05-31 13:45 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 ` Charles Wilson [this message]
2010-05-31 17:02 ` "TakeoffGW" Christopher Faylor
2010-05-31 18:25 ` "TakeoffGW" Andy Koppe
2010-05-31 23:43 ` "TakeoffGW" Charles Wilson
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C03BD54.4030801@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).