X-Spam-Check-By: sourceware.org From: ericblake AT comcast DOT net (Eric Blake) To: "Mohankumar Periasami" , cygwin AT cygwin DOT com Subject: Re: tar --exclude not working Date: Wed, 14 Feb 2007 14:52:53 +0000 Message-Id: <021420071452.4399.45D32245000CC5D30000112F22135753330A050E040D0C079D0A@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 4 2006) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > I'm using tar (GNU tar) 1.16.1 and have an archive with the following entries. > Files/report1.html > Files/report2.html > Files/report3.html > Files/report4.html > D:/Bkp/sol/ > D:/Bkp/sol/test1.pl > D:/Bkp/sol/test2.pl > D:/Bkp/sol/test3.pl > > Whenever, I try to exclude files starting with "D:/" its not working > as expected. Tar has special treatment of command-line arguments with colons, trying to treat it as a path to a remote machine. Tar archives created with drive letters are inherently non-portable, and under cygwin, you should create tar archives using a POSIX name such as /cygdrive/d rather than d:/ (or whatever you mount your cygdrive as). > > Is this a bug? Can it be worked atound? I have done nothing in this regards that is cygwin-specific. If it is a bug, then it is an upstream one. But more likely, it is merely a matter of your using drive letters when tar tries to interpret them as remote machine names. -- Eric Blake volunteer cygwin tar maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/