From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request new Ruby release
Date: Sat, 05 May 2018 00:57:00 -0000 [thread overview]
Message-ID: <5aed015b.1c69fb81.6a87b.524b@mx.google.com> (raw)
In-Reply-To: <c7343c4c-d1e8-1356-138a-6b3e72082852@gmail.com>
On Fri, 4 May 2018 15:16:49, Marco Atzeri wrote:
> 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.
such comments are perfectly acceptable if maintainers are acting in bad faith
with regard to packages. no one is perfect, certainly not myself. and if the
person in question is a maintainer of an important package, for example GCC or
Ruby, it is not acceptable for them to let a year or 2 go by without an update.
if they are worried about bugs, cygwin has a system in place for many years now
to deal with that. you make a package "[test]", so that people can test it. if
a maintainer cannot faithfully keep up with a package at least once a year,
that person should step aside as im sure other would be willing (myself
included) to take up maintainership of said packages.
> 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
sorry, did you really just invoke fortran as a serious argument? fortran is
arguably the oldest programming language still in use, if you can even call it
that. you cant even do HTTP with it:
http://rosettacode.org/wiki/HTTPS#Fortran
youll notice that ADA already got the axe:
http://github.com/cygwinports/cygwin64-gcc/blob/master/cygwin64-gcc.cygport#L52
this could happen to fortran as well.
> 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
so did i:
http://github.com/svnpenn/glade/tree/master/mingw-w64-x86-64/gcc
my GCC build is done, as soon as I finish my G++ build, I had planned to publish
my recipe, but i guess now is as good time as any. i dont have the patch files
as ive seen with other build, so im sure i am missing something.
--
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:[~2018-05-05 0:57 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
2018-05-05 0:57 ` Steven Penny [this message]
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=5aed015b.1c69fb81.6a87b.524b@mx.google.com \
--to=svnpenn@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).