Guessing this is a side effect of the build process, but as it stands, once you "unzip" the archive, on both Linux & MacOS, even the owner doesn't have permission to open or execute any of the files in the archive.
On linux it looks like this:
d--------- 6 root root 4096 Jan 15 09:23 'ApolloExplorer 1.1.3'
-rw-r--r-- 1 user user 33026329 Feb 11 10:21 ApolloExplorer.1.1.3.zip
and
d--------- 2 root root 4096 Feb 11 10:19 .
d--------- 6 root root 4096 Jan 15 09:23 ..
---------- 1 root root 101 Jan 6 14:45 README.txt
---------- 1 root root 376312 Jan 6 13:54 acp
---------- 1 root root 1074438 Feb 11 10:17 apolloexplorer_1.1.3-0_amd64.deb
On MacOS it looks like this:
In both cases you can "sudo" and "chmod" and fix it, but it's something that should be easily fixed in the archive.
Thanks again for a great tool!
Guessing this is a side effect of the build process, but as it stands, once you "unzip" the archive, on both Linux & MacOS, even the owner doesn't have permission to open or execute any of the files in the archive.
On linux it looks like this:
and
On MacOS it looks like this:
In both cases you can "sudo" and "chmod" and fix it, but it's something that should be easily fixed in the archive.
Thanks again for a great tool!