Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: strange source packaging? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 19 Apr 2002 22:28:06 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Earnie Boyd" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3JCSQP28777 > -----Original Message----- > From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] > Sent: Friday, April 19, 2002 3:13 AM > I'll add another penny to make it 2c. I agree with Chris > that I'd rather already have the patch applied. Why? If it's for ease of use, then fine - I agree that what the user receives should be patched. However that is somewhat orthogonal to how the download is accomplished. > I > differences from pristine supplied would be nice but if I > really care I would go and find the originals. That's not actually the point. The point is that with some minor setup.exe tweaking, the source download can be done it two parts: 'pristine' + (patch[es] & scripts). Then when a local adjustment is made, but the upstream hasn't released a new version, users can get the new source trivially - setup should be smart enough to see the pristine tarball in the /usr/src (or wherever) directory and just download the appropriate patch set. Rob