X-Spam-Check-By: sourceware.org
Message-ID: <46567595.8010605@qualcomm.com>
Date: Thu, 24 May 2007 22:35:17 -0700
From: Rob Walker <rwalker AT qualcomm DOT com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: make-3.81 update?
References: <46565CBE DOT 7020401 AT qualcomm DOT com> <20070525041200 DOT GA14393 AT ednor DOT casa DOT cgf DOT cx> <46566982 DOT 7000006 AT qualcomm DOT com> <46566B88 DOT 5AF84360 AT dessent DOT net>
In-Reply-To: <46566B88.5AF84360@dessent.net>
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

Brian Dessent wrote:
> Rob Walker wrote:
>
>   
>> My situation is this: I cannot advocate an off-the-rack Cygwin
>> installation for my team or my customers.  My current choices are:
>>
>>    1. supply an in-house compiled Cygwin version of make-3.81 (without
>>       cygwin1.dll, of course) that has the patch, with installation
>>       instructions and caveats
>>    2. supply an old Cygwin make-3.80 (with similar instructions and
>>       /more/ caveats)
>>    3. tell my customers and team to "figure it out"
>>
>> Is the CVS version with its bugs worse (calls for some subjectivity)
>> than the current Cygwin make-3.81-1?  Are the bugs new since 3.81-1?
>> Can Cygwin take *just* the "colon in paths" patch?
>>     
>
> 4. Package whatever version of make you desire in the Cygwin package
> format with a package version number that's numerically higher than
> what's on the official mirrors, put it on a server somewhere, create a
> setup.ini for it, and have your customers add that URL as as an
> additional installation mirror in setup.exe in addition to whatever
> normal mirror they use.
>
> 5. Provide a simple script that automatically fetches and installs the
> updated files (we're talking about a single 150KB executable here, how
> hard is this?) and fudges the /etc/setup/installed.db so that it will
> not be accidently uninstalled/overwritten by future runs of setup.
>   
Thanks, Brian, for the education.  I didn't know that these were options.

I hope you'll agree that your suggested 4 and 5 are functionally and 
"customer-educationally" equivalent to 1.

-Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/