You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty new to Keka but found it useful as an archiver for macOS, which knows and is able to work with many existing archive formats.
However, I've noticed that there is no "Test archive" function and the feature request is there for a while. So, I've created a script to do this. It is based on Keka and is able to test individual archive, list of different archives (1 file per loop iteration), recognize folders, and takes all files from them for testing. You could provide files as parameters manually, drag-n-drop them into a shell or choose interactively using macOS file choose dialogue.
The script outputs results into the terminal and optionally could send notifications to macOS Notification Center.
I've tried to use it as Automator's Quick Action, but am stuck with Automator's list of default shells and lack of informative debugging, so my script just fails there silently. If someone has success with this, please let me know here or using Issues in the repo, so I'll align with your steps and publish the guide for everyone.
I've started the topic with a question: how to map archive types to corresponding Keka modules correctly and whether we need to test tar containers separately in case they are used as intermediate packages before archiving (like *.tar.gz)?
I didn't get the answer, so I've implemented the script based on my own understanding with a fallback solution to test unknown files by 7z and UnAr before giving up on them. Please review that part and let me know if there is a better implementation or how some additional archive types could be handled.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi All,
I'm pretty new to Keka but found it useful as an archiver for macOS, which knows and is able to work with many existing archive formats.
However, I've noticed that there is no "Test archive" function and the feature request is there for a while. So, I've created a script to do this. It is based on Keka and is able to test individual archive, list of different archives (1 file per loop iteration), recognize folders, and takes all files from them for testing. You could provide files as parameters manually, drag-n-drop them into a shell or choose interactively using macOS file choose dialogue.
The script outputs results into the terminal and optionally could send notifications to macOS Notification Center.
You could find a script (as well as my other scripts) here: https://bitbucket.org/LazyDevelopment/shell-tools/src/master/
I've tried to use it as Automator's Quick Action, but am stuck with Automator's list of default shells and lack of informative debugging, so my script just fails there silently. If someone has success with this, please let me know here or using Issues in the repo, so I'll align with your steps and publish the guide for everyone.
I've started the topic with a question: how to map archive types to corresponding Keka modules correctly and whether we need to test tar containers separately in case they are used as intermediate packages before archiving (like *.tar.gz)?
I didn't get the answer, so I've implemented the script based on my own understanding with a fallback solution to test unknown files by 7z and UnAr before giving up on them. Please review that part and let me know if there is a better implementation or how some additional archive types could be handled.
Feel free to provide your feedback)
Beta Was this translation helpful? Give feedback.
All reactions