public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Keith Christian <keith1christian@gmail.com>
To: Brian.Inglis@systematicsw.ab.ca, cygwin@cygwin.com
Subject: Re: Future of 32-bit distro
Date: Fri, 12 Jan 2018 19:33:00 -0000	[thread overview]
Message-ID: <CAFWoy7GjX=uZVW0nMLGn7+=WCRkJJtA6dEuG_YJx_WVVqD-Tpg@mail.gmail.com> (raw)
In-Reply-To: <3e65ad8a-3ba1-9e6b-ccb6-afee9a8df9ba@SystematicSw.ab.ca>

I run the 32 bit Cygwin on a 64 bit Windows 7 machine and install
everything, because it has been unnecessary to waste time picking and
choosing packages even though I don't use them all.  I've been doing
this for years and suspect many other Cygwin aficionados do the same.

I asked a related question In this link:
https://cygwin.com/ml/cygwin/2016-11/msg00014.html and was offered
this command line to remove KDE and Gnome:

                setup-x86.exe -c GNOME,KDE


My first question was how to remove both KDE and Gnome which are
already installed, and I used the suggested command to successfully
remove the existing KDE and Gnome categories:

When I updated Cygwin a few weeks later, I did not know how to omit
KDE and Gnome during the install/update on the setup-x86.exe command
line so KDE and Gnome were re-installed.

For me, a final solution is the set of switches to tell setup-x86.exe
to install everything EXCEPT KDE and Gnome.

With KDE and Gnome out of the picture, I'd think there would be plenty
of space for those people who find 32 bit Cygwin perfectly
satisfactory, despite the fact that (by now, I assume) 64 bit and 32
bit have feature equality.

--
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

  reply	other threads:[~2018-01-12 19:33 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 [this message]
     [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       ` Future of 32-bit distro David Stacey
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='CAFWoy7GjX=uZVW0nMLGn7+=WCRkJJtA6dEuG_YJx_WVVqD-Tpg@mail.gmail.com' \
    --to=keith1christian@gmail.com \
    --cc=Brian.Inglis@systematicsw.ab.ca \
    --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).