public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request new Ruby release
Date: Fri, 04 May 2018 13:16:00 -0000	[thread overview]
Message-ID: <c7343c4c-d1e8-1356-138a-6b3e72082852@gmail.com> (raw)
In-Reply-To: <5aec4d68.1c69fb81.f5182.7ad5@mx.google.com>

On 5/4/2018 2:09 PM, Steven Penny wrote:
> On Fri, 4 May 2018 00:05:23, Brian Inglis wrote:
>> For an understaffed, all-volunteer effort, Cygwin does a tremendous job
>> providing us with a compatible, reliable, stable subsystem working 
>> environment,
>> running in a less stable environment.
>> Cygwin seems to keep up to date with stable releases of important 
>> packages
>> better than distros who have full time staff, many more volunteers, 
>> and don't
>> also have to deal with an alien environment.
> 
> Cygwin is a fantastic project. and yaakov handles a massive amount of 
> packages,
> and i commend him for that. but lets not kid ourselves, ok? cygwin 
> *does* keep
> up to date with *some* important packages as you say, but not other 
> important
> packages. for example, GCC, is over a year old:

Steven,
I do not see you doing any package activity release,
so you should refrain to comment on how we (package maintainers)
use our own spare time for this project.

Please note that sometime, things are broken upstream
and it takes time and it could require not available capability to
solve the issues.
https://gcc.gnu.org/ml/fortran/2018-03/msg00014.html

If you want to help for a new package release that you care,
try to build it, check that every thing is in place,
provide if needed patches and guidance and I am almost sure
the relative maintainer will appreciate your effort.
I surely did
https://sourceware.org/ml/cygwin/2018-02/msg00142.html

Regards
Marco





--
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-05-04 13:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24 20:51 Steven Penny
2018-05-03 23:17 ` Steven Penny
2018-05-04  3:09   ` Yaakov Selkowitz
2018-05-04  6:05   ` Brian Inglis
2018-05-04 12:09     ` Steven Penny
2018-05-04 13:16       ` Marco Atzeri [this message]
2018-05-05  0:57         ` Steven Penny
2018-05-05  3:41           ` Brian Inglis
2018-05-05  5:27           ` Marco Atzeri
2018-05-05  6:56             ` Steven Penny
2018-05-05 16:18               ` Stephen John Smoogen
2018-05-06  5:54               ` Yaakov Selkowitz
2018-05-06 14:08                 ` Steven Penny
2018-05-14 16:10                   ` cyg Simple
2018-05-15  4:17                     ` Steven Penny
2018-05-15 13:27                       ` What is Cygwin and MinGW [WAS: Request new Ruby release] cyg Simple
2018-05-15 14:37                       ` Request new Ruby release Adam Dinwoodie

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=c7343c4c-d1e8-1356-138a-6b3e72082852@gmail.com \
    --to=marco.atzeri@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).