I've wonder this myself. They have https://mikrotik.com/downloadterms.html . Not a lawyer but comes down to if winbox is encompassed by the "MIKROTIK ROUTEROS SOFTWARE ROUTER SYSTEM" since they do say:
And, I do know @normis chastises people for using "third-party packages", but they seem to allow the brew package with winbox for Mac on GitHub.
Personally, the better way would be if the snap package were to have the needed wine bits BUT then downloaded winbox from Mikrotik as part of some post-install task. So winbox itself wouldn't be in a package repo. This is a safer approach since theoretically the post-install could verify Mikrotik's SSL cert when downloading winbox. The brew package for winbox just includes winbox, which works but I'd actually prefer if it downloaded it from Mikrotik not GitHub.
Why Mikrotik didn't long ago just package wine with winbox for Linux and Mac (via MacPort and/or brew) themselves I have no idea. Instead, rumors are there is some future multi-platform client coming. So they let Linux and Mac users suffer with which version of wine works in the meanwhile. While wine being bundle in a distro package (e.g. like the brew one) would solve 80+% of the need for some "Multiplatform" client IMO.
You may not:
permit other individuals to use the SOFTWARE except under the terms listed in Article 1 "Grant of License" above;
modify, translate, reverse engineer, decompile, disassemble (except to the extent applicable laws specifically prohibit such restriction), or create derivative works based on the Software;
copy the Software; or
remove any proprietary notices or labels on the Software.
And, I do know @normis chastises people for using "third-party packages", but they seem to allow the brew package with winbox for Mac on GitHub.
Personally, the better way would be if the snap package were to have the needed wine bits BUT then downloaded winbox from Mikrotik as part of some post-install task. So winbox itself wouldn't be in a package repo. This is a safer approach since theoretically the post-install could verify Mikrotik's SSL cert when downloading winbox. The brew package for winbox just includes winbox, which works but I'd actually prefer if it downloaded it from Mikrotik not GitHub.
Why Mikrotik didn't long ago just package wine with winbox for Linux and Mac (via MacPort and/or brew) themselves I have no idea. Instead, rumors are there is some future multi-platform client coming. So they let Linux and Mac users suffer with which version of wine works in the meanwhile. While wine being bundle in a distro package (e.g. like the brew one) would solve 80+% of the need for some "Multiplatform" client IMO.
Statistics: Posted by Amm0 — Wed Feb 21, 2024 6:32 pm