Wrong permissions for the downloaded toolchain about arduinocore-bouffalo HOT 10 OPEN

Will take look, thanks

from arduinocore-bouffalo.

@pfeerick the reason why is everything hosted on PINE64 Cluster is because many times Github CDN is terribly slow and I wait ages until it downloads something. Anyway, I think we can have multiple "mirrors". I'm open to merge your work @pfeerick here.

from arduinocore-bouffalo.

I've made some tests few days ago, and without special flags the permissions seemed to be kept after a zip and an unzip, but I don't know if there are default parameters on my distro. 🤷

For the hosting, maybe the Pine64 cluster could regularly pull the files from the Github repo ?
So we would have the speed of Pine64, and the last updates of Github.

from arduinocore-bouffalo.

Just to add that this problem still exists in Linux, it is needed to run:

cd ~/.arduino15/packages/bouffalo/tools/riscv64-unknown-elf/0.0.1/bin
chmod +x *
cd ~/.arduino15/packages/bouffalo/tools/riscv64-unknown-elf/0.0.1/libexec/gcc/riscv64-unknown-elf/8.3.0
chmod +x *

from arduinocore-bouffalo.

I'll be looking into this this week, in pfeerick/ArduinoCore-bouffalo-packages#1

I think the underlying issue is the choice of archive... a zip was used instead of a tar, which would preserve file permissions. Not a issue for windows, but it is for linux and mac.

from arduinocore-bouffalo.

This could be good indeed, though if a zip file is needed, I think that if the archive is made on linux, it keeps the permissions.

from arduinocore-bouffalo.

from arduinocore-bouffalo.

@gamelaster I'm not complaining about the files being on the pine64 cluster, more that they are a black box at the moment, with no idea as to the source of the files, or how the packages were put together ;) For example, where do the toolchains come from? Because knowting that, the next question is, is it possible to get an arm64 toolchain happening as well? i.e. lets get a little pinebook pro love happening as well ;)

Hence why I'd ideally like to automate generation of the various packages via a github action if practical, and which also means the upload / generation of the files is all done on the github side, and then simply mirrored to the pine64 cluster if that's faster / more reliable at times. Plus it makes the builds reproducible. The packages repo I've got might just turn into a bunch of scripts, which generate a release, which all the binaries... don't quite know how it will play out just yet.

The other aspect to this is once I know enough about the full layout, I can look at getting a PlatformIO platform package going also...

from arduinocore-bouffalo.

@pfeerick well, you made really good points, having a mirror is good. I will think about this.

from arduinocore-bouffalo.

Somehow still an issue

from arduinocore-bouffalo.