From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Future of 32-bit distro
Date: Sat, 13 Jan 2018 09:11:00 -0000 [thread overview]
Message-ID: <ec5514e4-d603-8290-b9ec-dabd3168e0b3@tiscali.co.uk> (raw)
In-Reply-To: <c5811365-3b30-5cd6-e4fe-c72fd26d618d@cygwin.com>
On 12/01/18 18:11, Yaakov Selkowitz wrote:
> If it is not possible for the entire 32-bit distribution to function as
> a whole, is it time to reconsider how much we provide for 32-bit? And
> when can we just drop 32-bit entirely?
I suspect there are a great number of people running 32-bit Windows,
even if the underlying hardware is capable of running 64-bit. For that
reason, I would argue against dropping 32-bit support at the moment -
even if it increases my work as a package maintainer.
Would it be possible for 'setup_x86.exe' to give a warning if run on a
64-bit OS? That might help.
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-01-13 9:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 12:31 rebase-4.4.3-1 regression: Too many DLLs for available address space Christian Franke
2018-01-11 16:06 ` Corinna Vinschen
2018-01-11 17:53 ` Achim Gratz
2018-01-11 17:56 ` Corinna Vinschen
2018-01-11 21:52 ` Denis Excoffier
2018-01-12 9:13 ` Corinna Vinschen
2018-01-12 18:11 ` Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space) Yaakov Selkowitz
2018-01-12 19:02 ` Future of 32-bit distro Brian Inglis
2018-01-12 19:33 ` Keith Christian
[not found] ` <7218003ac95dc6814bbb309dda3df748@smtp-cloud8.xs4all.net>
2018-01-13 1:56 ` Brian Inglis
2018-01-13 2:15 ` Keith Christian
2018-01-12 19:40 ` Steven Penny
2018-01-12 20:20 ` Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space) Vince Rice
2018-01-12 22:00 ` Keith Christian
2018-01-13 9:11 ` David Stacey [this message]
2018-01-12 17:16 ` rebase-4.4.3-1 regression: Too many DLLs for available address space Thomas Waldmann
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=ec5514e4-d603-8290-b9ec-dabd3168e0b3@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin@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).