X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4C61BEEF.1020301@qualcomm.com>
Date: Tue, 10 Aug 2010 14:04:47 -0700
From: Rob Walker <rwalker AT qualcomm DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: [ANNOUNCEMENT] Update on status of make-3.82 release for cygwin
References: <announce DOT 20100810175435 DOT GA27225 AT ednor DOT casa DOT cgf DOT cx> <4C61B2F5 DOT 2040409 AT qualcomm DOT com> <20100810202148 DOT GA27734 AT ednor DOT casa DOT cgf DOT cx>
In-Reply-To: <20100810202148.GA27734@ednor.casa.cgf.cx>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 8/10/2010 1:21 PM, Christopher Faylor wrote:
> On Tue, Aug 10, 2010 at 01:13:41PM -0700, Rob Walker wrote:
>    
>> On Cygwin, make-3.82 supports DOS paths by default.  I'm curious about
>> what work might be involved in re-enabling the --ms-dos option, and I'd
>> like to help, if I can.
>>
>> I built my Cygwin make-3.82 packages directly from the upstream release
>> tarball using the attached script.
>>      
> I don't need help.  I've been building make for years so I obviously
> don't need your script.
>
>    

Sorry for the confusion: I was not offering my script as "hey look, 
here's how you do it", I was more saying "I did it this way, but maybe 
that's too simple.  What else is involved, and can I help with that?"

So: I'm still curious about the work you anticipate might be required.  
There's not much on the Cygwin site detailing the responsibilities of a 
package maintainer beyond:

    /Do you have the time to maintain the package?/
    Packages without active maintainers are pulled from the
    distribution. Generally speaking the time commitment is relatively
    low, simply subscribe to the cygwin mailing list. We'd prefer if you
    read the non-digest mode since prompt response to packaging issues
    is a plus. When a /bug/ in your package is reported in the cygwin
    mailing list, address the bug (if it's a Cygwin-only bug) or pass
    back to the vendor. When a solution exists, create an updated
    package with the fix in it, and send a notification that you need
    the package uploaded to cygwin-apps. Note that you are not expected
    to be a helpdesk for the package - the users should be pointed to
    the vendors lists if you've determined that the bug is not a
    Cygwin-related bug.

Thanks,
Rob


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