Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm list-help: list-post: Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-apps AT sourceware DOT cygnus DOT com Date: Mon, 15 May 2000 14:42:54 -0400 From: Chris Faylor To: cygwin-apps AT sourceware DOT cygnus DOT com Subject: Re: [jorg DOT schaible AT db DOT com: Setup and zlib, libpng] Message-ID: <20000515144254.A1937@cygnus.com> Mail-Followup-To: Chris Faylor , cygwin-apps AT sourceware DOT cygnus DOT com References: <20000515180038 DOT 21004 DOT qmail AT web113 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <20000515180038.21004.qmail@web113.yahoomail.com>; from earnie_boyd@yahoo.com on Mon, May 15, 2000 at 11:00:38AM -0700 On Mon, May 15, 2000 at 11:00:38AM -0700, Earnie Boyd wrote: >--- DJ Delorie wrote: >> My original intent was to avoid this problem: Port version X. Version >> Y released; version X deleted. Time to port version Y. What did you >> change? With no base sources to diff against, you're out of luck. >> >> So, I had hoped we could somehow keep enough information in the >> distribution to be able to know, quickly, what was involved in the >> port. >> >> The diff would always be against the original sources, i.e. they're >> what we needed to add to do the port. > >Personally, if I as a user download the source file from the cygwin >sight or mirror I would like it to configure and make without applying >a patch. I agree. I don't think that this invalidates what DJ said, though. We could still keep a .diff file in the distribution that shows how we got to the current state. cgf