Subj : Unpack Cmd junk paths and downloads
To   : g00r00
From : Bj”rn Wiberg
Date : Sun Aug 08 2021 09:19 pm

Hello g00r00!

It is my understanding that the Unpack Cmd of archivers should junk paths to make sure that Mystic will find the extracted file in the root of the temp directory, e.g. when (V)iewing an archive (non-built-in formats) and choosing to (D)ownload a file. Is that correct?

As you already know, some archivers (e.g. tar) require archive members to be specified by their full path when extracting parts of (specific files from) an archive.

Right now I'm having the issue that albeit I can specify the path to an archive member at the (D)ownload file name prompt -- e.g. subdir/test2.txt -- which is great! -- the extracted file will (because of "junk path" flags to the
archiver) end up as test2.txt in the top of the temp directory. Mystic fails to find the file as subdir/test2.txt inside the temp directory, and does nothing (you get no file).

If you (D)ownload again, and this time specify test2.txt, it will actually fail to extract it (you didn't specify a full path this time!), but find the previously junk-path-extracted test2.txt, and give you that for download.

Shouldn't Mystic be looking for the basename of the entered File Name when trying to locate the extracted file for download?

(But *do* allow for the entered File Name to be a path -- just as it is now! -- as some archivers require it.)

Best regards
Bj”rn

--- Mystic BBS v1.12 A47 2021/08/08 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

.