From: Vince Rice <vrice@solidrocksystems.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Statistics and curiosity
Date: Fri, 11 Jan 2019 17:13:00 -0000 [thread overview]
Message-ID: <B870AA82-F0B7-4DBB-A1C9-3CF055325E3F@solidrocksystems.com> (raw)
In-Reply-To: <20190111164353.GD593@calimero.vinschen.de>
> On Jan 11, 2019, at 10:43 AM, Corinna Vinschen wrote:
>
> On Jan 11 16:40, Lemke, Michael ST/HZA-ZIC2 wrote:
>> On Friday, January 11, 2019 5:30 PM Corinna Vinschen wrote:
>>> On Jan 11 16:15, 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
>>>
>>> If somebody is willing to maintain apt-get as package in the Cygwin
>>> distro, which includes keeping it running if setup.exe changes, fixing
>>> bugs as required(*), by all means, go ahead.
>>>
>>> Are you volunteering, by any chance?
>>
>> My reply was only meant as a hint, I have no interest in the package,
>> but someone (who is on this list I believe) already did:
>>
>> https://github.com/cup/sage/issues/20
>
> Nice.
No, actually, it's not nice at all. See https://github.com/transcode-open/apt-cyg/issues/73 and read down to alphapapa's comment. A little googling will show the comment is accurate.
--
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 17:13 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 [this message]
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=B870AA82-F0B7-4DBB-A1C9-3CF055325E3F@solidrocksystems.com \
--to=vrice@solidrocksystems.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).