this is not to directly answer your question, more as an aside note, but since you said that you did not like Apple's "packaging" system, but are apparently not willing to switch to Linux, you might be interested in the fifty-fifty solution. There are package managers that are though for Linux systems (and they work pretty much like most Linux package managers), but that work on MacOS too.
If I understand it correctly, OP already took this 50-50 approach by using Pacman (Archlinux's package manager). The jsoftware packaged there, however, for some reasons, can not run jqt.
This might be a good way for you to circumnavigate Apple's all mighty surveillance without completely changing most of your workflow / setup. For instance, you could take a look at nix (which packages J). I am not sure whether nix packages JQt, but if it doesn't you can always to on their github repository and open an issue in which you ask for it to be packaged (or even package it yourself!), and it should be done within next version (usually).

I am a nixos user myself and there's only jconsole! Jqt is NOT packaged in nix. I am not an expert and couldn't add jqt to the package myself (got compilation error I don't remember). I had to use pre-compiled jqt for my amd64 and arm64 linux machines, but that's not portable the way jconsole already is.

The nix team is small and already busy with more mainstream packages, so simply requesting for some package won't work. A pull request, however, will receive feedback and/or approval quickly.

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to