From: David Dombrowsky <6thstreetradio@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Statistics and curiosity
Date: Sun, 13 Jan 2019 01:49:00 -0000 [thread overview]
Message-ID: <0eb5e1b2-551e-c80c-a815-ae2b14480ac8@gmail.com> (raw)
In-Reply-To: <AM6PR03MB3558D3278B77A7B27D769591BE850@AM6PR03MB3558.eurprd03.prod.outlook.com>
On 1/11/19 11:15 AM, Lemke, Michael ST/HZA-ZIC2 wrote:
> On Friday, January 11, 2019 3:50 PM David Dombrowsky wrote:
>> On 1/11/19 8:40 AM, E. Madison Bray wrote:
>>> 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.
>>
>> YES PLEASE! Cygwin is awesome and this would put it firmly into the
>> first class of required windows programs/systems.
>
> It's dead:
>
> https://github.com/transcode-open/apt-cyg/blob/master/status.md
Bring Out Yer Dead!
What about package managers that don't interact with cygwin setup? Why
not build `apt-get` et. al. to install to /opt/? Yes I know it would be
a system within a system within a system, but it might be worth a shot.
This, especially if the "cygwin setup" package manager isn't open
source (I thought everything cygwin was, but I guess not).
--
David Dombrowsky, Software Engineer
davek@6thstreetradio.org | 518-374-3204
https://www.linkedin.com/in/david-dombrowsky-94334415
--
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-13 1:49 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 [this message]
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=0eb5e1b2-551e-c80c-a815-ae2b14480ac8@gmail.com \
--to=6thstreetradio@gmail.com \
--cc=cygwin@cygwin.com \
--cc=davek@6thstreetradio.org \
/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).