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 Message-ID: <03F4742D8225D21191EF00805FE62B9908E23EC6@aa-msg-01.medstat.com> From: John Wiersba To: "'cygwin'" Subject: RE: two problems with cygwin's zip Date: Tue, 26 Jun 2001 14:09:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 26 Jun 2001 18:09:52.0697 (UTC) FILETIME=[32677290:01C0FE6B] > -----Original Message----- > From: Fred T. Hamster [mailto:fred AT gruntose DOT com] > Sent: Tuesday, June 26, 2001 12:04 PM > To: cygwin AT cygwin DOT com > Subject: Re: two problems with cygwin's zip > > > the first problem (of seeing absolute paths in zips) occurs > when using > forward slashes as well. it's an absolute path issue rather than a > slash-handedness issue. thus, this is still a bug relevant > to cygwin's > zip, even if we must discount slash issues in paths. but i don't > suggest that we abandon those issues... My version of zip seems to remove leading / in the archive? Yours doesn't? $ /usr/bin/zip ./asdf.zip /bin/ls.exe adding: bin/ls.exe (deflated 53%) <= note: no leading / > it seems pretty disturbing to me that a unix emulation environment > running under ms-windows would have many problems parsing > ms-dos paths. I agree with the previous responses about this. Cygwin's job is not to port every tool to handle Windows pathnames natively, but to allow unix tools to function in a unix-like way under Windows. What about using cygpath to convert the paths before passing them to zip? -- John Wiersba -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/