Open GoogleCodeExporter opened 8 years ago
The issue here is xar currently prints out the path within the archive, not the
path given. Xar does some path
munging when you archive something, stripping out leading / and extraneous
///'s and ../../../../'s. We only get
the munged path back from xar_add() or xar_extract() after the file has been
archived or extracted.
So, we could print the file path before the file is added/extracted, but it
would be a different file path from what
is currently being printed.
Original comment by bbraun
on 21 Apr 2007 at 6:05
Maybe have -v be prior to archival (file-system path) and -V post archival
(archive path)
Original comment by psa...@gmail.com
on 24 Oct 2007 at 3:23
Original issue reported on code.google.com by
bbraun
on 19 Apr 2007 at 10:37