I think it is dangerous for pkt to always use the absolute pathname when unpacking; it should by default unpack starting from the current directory and make unpacking to the actual stored pathname an option.
pkt will unpack from the current directory if its set when the pkt file was created.
for example if you created the file using ./foo instead of /fullpath/foo it will unpack relatively (from the current directory to foo/). The GUI tends to specify the full path, but you can do it from the CLI normally.
My concern then is that if person A creates the archive and person B unpacks it, then person B might have sensitive files overwritten unexpectedly.
hmm...i'll put in a relative flag which will probably solve this.
That is exactly what I had in mind; although it would be safer if the default was relative (akin to tar). 'Least Surprise' and all that; no other archiver defaults to absolute-paths.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.