The tar utility that comes as a part of UnxUtils is a "native port" and accepts fully specified paths. Eg. This works fine:
tar -cf c:\X.tar X
I've generally found these native ports work better (from cmd.exe) than those that rely upon the cygwin dlls.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply]
[d/l]
[select] |
Once upon a time, I played around with using jar files as a platform agnostic solution since tar(1) understands jar files...that was, admittedly in an environment whereby java was installed on every machine to which deliveries had to be made.
IIRC, I even prototyped an ABI package lookalike solution using that as a basis.
A user level that continues to overstate my experience :-))
| [reply] |
A .jar file is actually a .zip file plus some extras in its content (I think a MANIFEST file, but I'm not sure that's all...?). And .zip and .gz are related, they're both handled by zlib (and thus, by Compress::Zlib too — usually through Archive::Zip). Plenty of tar binaries can directly handle .tar.gz, compressed .tar files. So maybe there is your link.
| [reply] |
Ahh...Thank you very much, BrowserUk! The native port of Tar in UnxUtils works perfectly! | [reply] |