From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 112730 invoked by alias); 5 May 2018 00:57:04 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 112720 invoked by uid 89); 5 May 2018 00:57:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Gm-Message-State:sk:ALKqPwc, H*M:1c69fb81, faithfully, faith X-HELO: mail-it0-f68.google.com Received: from mail-it0-f68.google.com (HELO mail-it0-f68.google.com) (209.85.214.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 05 May 2018 00:57:02 +0000 Received: by mail-it0-f68.google.com with SMTP id j186-v6so5501222ita.5 for ; Fri, 04 May 2018 17:57:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:subject:to:references :user-agent; bh=ZJeU2TIQkV9bGtrOxRwt75gDxO1Sb+7RHfZy8MFKXzk=; b=mZMD6OPqb3BifEughkzLShjkAGjvvmjJGFQWunDzjAFvT85EFZPouHw9Mdua3oGY0Y 5+Ln6JiSwuuT+NTCCZnOs+vYNi+mbigs+/YC5YJ7XXve/3Bz8w4MzJfAx/ZKwInH6fa2 z37rWC163EGQ/zRiRkGj9Q5kueY6uo2ozah4HfnDKON+DKtKi6CsJYb5IfQi5wdh0SpR HJxyXBhFGEgk2hQu3mRl5/KYCzYbkcf5ah83DhY7DsuIkylGGuSXdUTWlk70ikxVlVZg 9E5lCi9Yr7Ec2o+6jLgNtLxsEhlz7Za1vYpyTdxeZqkwabcZtErE5RLLk+JGwS+c55sm KG1g== X-Gm-Message-State: ALKqPwcDma9RvubKxu/kn1/KFq9pZ0vUzeXmTo44vRcbCXIKSCUN+cOO +v3Job/LwuexSYIxY7/u5cqpVg== X-Google-Smtp-Source: AB8JxZqMlI9lxDAToXOwIQAEtJPBlS6hlZPAXaumii4vFBt7uq33DHr8PFbt2nluAHJbc0qQBgjplw== X-Received: by 2002:a24:6793:: with SMTP id u141-v6mr1450740itc.0.1525481820125; Fri, 04 May 2018 17:57:00 -0700 (PDT) Received: from yrR ([2605:6000:9fc0:56:c2a:f066:2911:f71b]) by smtp.gmail.com with ESMTPSA id j7-v6sm870952ioe.67.2018.05.04.17.56.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 May 2018 17:56:59 -0700 (PDT) Message-ID: <5aed015b.1c69fb81.6a87b.524b@mx.google.com> Date: Sat, 05 May 2018 00:57:00 -0000 From: Steven Penny X-Google-Original-From: Steven Penny Subject: Re: Request new Ruby release To: cygwin@cygwin.com References: Content-Type: text/plain; charset=utf8; format=flowed User-Agent: Tryst/2.4.0 (github.com/svnpenn/tryst) X-SW-Source: 2018-05/txt/msg00082.txt.bz2 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