From: "Matt Seitz (matseitz)" <matseitz@cisco.com>
To: "Cygwin-L" <cygwin@cygwin.com>
Cc: "Warren Young" <warren@etr-usa.com>
Subject: 64-bit Cygwin packages (was RE: Is the Latest Release of Cygwin supported on Windows Server 8/2012)
Date: Tue, 22 May 2012 19:06:00 -0000 [thread overview]
Message-ID: <70952A932255A2489522275A628B97C31348C6E2@xmb-sjc-233.amer.cisco.com> (raw)
> From: Cygwin-L On Behalf Of Warren Young
>
> I would say that the vast majority of the packages in the Cygwin
> distribution could not reasonably make use of 64-bit data spaces.
>
> However, one of your arguments in this thread cuts both ways: the fact
> that there are a few packages that reasonably can do so means you cannot
> say "we don't need it".
If someone wants a 64-bit version of a packages in the distribution, then how about they build a 64-bit version of the package and report the results? That would give the distribution maintainers actual data about the costs and benefits.
next reply other threads:[~2012-05-22 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 19:06 Matt Seitz (matseitz) [this message]
2012-05-22 19:36 ` Cliff Hones
2012-05-22 20:03 ` marco atzeri
2012-05-22 20:15 Matt Seitz (matseitz)
2012-05-26 21:19 ` Christopher Faylor
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=70952A932255A2489522275A628B97C31348C6E2@xmb-sjc-233.amer.cisco.com \
--to=matseitz@cisco.com \
--cc=cygwin@cygwin.com \
--cc=warren@etr-usa.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).