Miha Kralj

I was young and stupid when I wrote the plugin, didn't really know what I am doing. That was my first adventure in making something for OPNsense and I am...

so, as you noticed, there are two speedtest implementations - the python one and the binary one. They can't co-exist as then have the same name; it is the one...

> Apparently it's already installed, well at least py39-speedtest-cli-2.1.3 is The nightmare of slippery names is a problem with both packages - Python and Binary. Therefore I updated the `install_speedtest.sh`...

@mimugmail do we have the exec flag set in the latest speedtest package? I cannot see the settings in the Github source tree - we should check that there is...

> if new/updated servers are all socket only why not just have the one binary option going forward and simplify? Ookla binary is not open source and Python CLI is....

I tested around and packager (`pkg create`) honors flags on the file as it packages it into the archive; we just need to set the flag right in the repo;...

that works too, but it is unnecessary if we set the +x flag on the file before packing it. Let me play with it.

https://github.com/mimugmail/opn-repo/pull/180 has +x flag set on .sh and .py files required for this plugin. Let's repackage and see if FreeBSD documentation is right...

this issue is ready to be closed.

Aren't these packages exactly the same as building them from ports? Risk is exactly the same, the difference is that building from ports demands the whole build chain of tools...