DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:references:subject
	:content-type; q=dns; s=default; b=g/dbqVJ4kPfA+UhKSli7XwDkrbkug
	lvtNfZJGosilqW2RAhTYLDuvnengpYFmenWqfV6p8p0HYRfT9PINoIo2fhKPZU0u
	AQ4t7lRoDRnrj1/hsIUbrKrBPpZEMQDiVHBvdoD2vA0bFVC/lOuBeToXo+E/H/VP
	tl/F0CTVVQ1LgA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5a5015b1.95e6ca0a.40dc0.180f@mx.google.com>
Date: Fri, 05 Jan 2018 16:17:53 -0800 (PST)
From: Steven Penny <svnpenn AT gmail DOT com>
To: cygwin AT cygwin DOT com
References: <CA+Fg1xZxhGnzEw_=FGi8sRq-iHSMtcfHYoZOGz7HRtVBBZowVg AT mail DOT gmail DOT com>
Subject: Re: flex package POSIX violation
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst)

On Fri, 5 Jan 2018 15:37:11, Gerrit Haase wrote:
> Maybe to 'request' something is not the best approach to resolve your issue?

yeah, sometimes it is. my original request was Dec 31 [1]. by Jan 1 [2], updated
package had been published.

> A better way to handle issues like this would be:
> you provide a patch to handle the issue and the maintainer of the
> package may then decide to incorporate your patch.

maybe you should read full threads before injecting your opinion. this advice
might hold true for larger changes - but we are literally talking about 1
symlink.

And even if that werent the case, this is open source. *I* decide my own level
of involvement, not you. if i want to make a half ass request with no effort,
that is my decision and it might take years or never for it to be implemented,
or it might be the next day as we see here. please look here [3] to see that i
am well versed on how to make a patch - cheers

[1] http://cygwin.com/ml/cygwin/2017-12/msg00296.html
[2] http://cygwin.com/ml/cygwin/2018-01/msg00004.html
[3] http://github.com/svnpenn


--
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