Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Thu, 13 Apr 2000 12:00:28 -0400 From: Chris Faylor To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: More setup changes Message-ID: <20000413120028.A12405@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: Chris Faylor , cygwin-developers AT sourceware DOT cygnus DOT com References: <20000413012229 DOT A11346 AT cygnus DOT com> <20000413114909 DOT C12180 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <20000413114909.C12180@cygnus.com>; from cgf on Thu, Apr 13, 2000 at 11:49:10AM -0400 On Thu, Apr 13, 2000 at 11:49:10AM -0400, cgf wrote: >>I do not know if this ever worked, but it is >>broken now so I whipped up a patch for the >>problem. This patch will append a \ char on >>the end of a filename that setup.c is processing. > >Thank you for the patch, but I don't see how it is correct to always add >a slash on the end of every file that is reported by tar. > >In most cases these are files that are being extracted. Oops. I entirely misread the patch. Sorry. You obviously aren't just indiscriminately copying a \ to the end of the filename. cgf