Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Mon, 29 Jan 2001 17:23:27 -0600 (CST) From: Mumit Khan To: Cygwin Mailing List Subject: Re: tar ball with illegal file names In-Reply-To: <3A75EAF8.73CCECE5@yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 29 Jan 2001, Earnie Boyd wrote: > tar --to-stdout -xf foo.tar foo:bar > foobar This is a great trick that I certainly didn't remember when the original question came up. Thanks. I remember thinking about this issue a while back, especially because my own software package has (had rather) filenames with colons (common in a section of VLSI CAD community way back) as well as directories called aux and such. 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. Regards, Mumit -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple