public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "E. Madison Bray" <erik.m.bray@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Statistics and curiosity
Date: Fri, 11 Jan 2019 13:40:00 -0000	[thread overview]
Message-ID: <CAOTD34Z9doPr1wcZRy9uc7jauZf=nVJfmMNO9e2gbLvzEqKZCw@mail.gmail.com> (raw)
In-Reply-To: <CAAD4mYgnuRwavk=hhr8mk7yWSNDAT5Q6h9kPO3uMwWu-asQtwQ@mail.gmail.com>

On Wed, May 2, 2018 at 1:23 AM R0b0t1 wrote:
>
> On Tue, May 1, 2018 at 7:49 AM, Marco Atzeri wrote:
> > Hi,
> > following a unpleasant discussion about cygwin usability
> > https://cygwin.com/ml/cygwin/2018-04/msg00364.html
> > I wondered how many users cygwin have.
> >
>
> Younger people seem to prefer MSYS due to its use of pacman.
> Admittedly, it is very convenient. Otherwise Cygwin (or MSYS) has
> always been accepted (at least amongst everyone I talk to) as a
> necessity.

(with apologies for replying to such an old thread; I've been trying
to do some email catchup)

I have often wondered why apt-cyg [1] hasn't been adopted fully by
Cygwin as one of the default packages (in fact I'm not sure if there
even is an actual cygwin package for apt-cyg), aside from the fact
that it's not formally maintained as part of the cygwin ecosystem.
Maybe it should be.

Although the old setup.exe has its uses, and isn't too bad when you
use the command-line flags either, almost always whenever I make a new
cygwin install, unless I know immediately what packages I'm going to
need, I usually just install the bare minimum I need to get apt-cyg
working (usually wget, plus a few other core utilities), and then use
apt-cyg from thereon out.  In my experience it works really well, and
is just as good as having pacman or whatever.


[1] https://github.com/transcode-open/apt-cyg

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

  parent reply	other threads:[~2019-01-11 13:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 12:50 Marco Atzeri
2018-05-01 21:07 ` Keith Christian
2018-05-01 23:22 ` R0b0t1
2018-05-02  5:32   ` Marco Atzeri
2019-01-11 13:40   ` E. Madison Bray [this message]
2019-01-11 14:49     ` David Dombrowsky
2019-01-11 16:16       ` Lemke, Michael  ST/HZA-ZIC2
2019-01-11 16:29         ` Corinna Vinschen
2019-01-11 16:40           ` Lemke, Michael  ST/HZA-ZIC2
2019-01-11 16:43             ` Corinna Vinschen
2019-01-11 17:13               ` Vince Rice
2019-01-13  1:49         ` David Dombrowsky
2019-01-13  2:32           ` Marco Atzeri
2019-01-13 22:36             ` Corinna Vinschen
2019-01-11 20:31     ` Achim Gratz
2019-01-11 22:16       ` E. Madison Bray
2018-05-02  5:41 ` Brian Inglis
2018-05-02  6:03 ` Marco Atzeri

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='CAOTD34Z9doPr1wcZRy9uc7jauZf=nVJfmMNO9e2gbLvzEqKZCw@mail.gmail.com' \
    --to=erik.m.bray@gmail.com \
    --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).