Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 29 Jan 2001 18:35:48 -0500 From: Christopher Faylor To: Cygwin Mailing List Subject: Re: tar ball with illegal file names Message-ID: <20010129183548.A4257@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin Mailing List References: <3A75EAF8.73CCECE5@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Mon, Jan 29, 2001 at 05:23:27PM -0600 On Mon, Jan 29, 2001 at 05:23:27PM -0600, Mumit Khan wrote: >I had considered a "translation table" that will map illegal names to >something that will be understood by underlying OS when extracting the >archive, and creating a "map" file in each directory that will contain >the translation to the original name. When creating the archive, the >map file will do the reverse translation. I did patch cvs to do this >back in B19 days, but who knows where that code is. Does this sound >like something worthwhile? fyi, gcc implements a very similar >mechanism, using a map file named header.gcc. I think that DJGPP already has something like this, actually. Did you adapt it from DJGPP by any chance? cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple