From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Cygwin Statistics and curiosity
Date: Fri, 11 Jan 2019 20:31:00 -0000 [thread overview]
Message-ID: <874lafey1v.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAOTD34Z9doPr1wcZRy9uc7jauZf=nVJfmMNO9e2gbLvzEqKZCw@mail.gmail.com> (E. Madison Bray's message of "Fri, 11 Jan 2019 14:40:10 +0100")
E. Madison Bray writes:
> 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.
For starters, apt-cyg and the handful of purported alternatives will
break your installation in subtle and not-so subtle ways. None of them
handle all postinstall actions correctly and all of them will fall over
if locked in-use files have to be altered or replaced.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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:[~2019-01-11 20:31 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
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 [this message]
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=874lafey1v.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).