Hello,
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. 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).
Cheers,
Adrien Mathieu
On 19/10/2021 18:26, John Baker wrote:
Greetings all,
I managed to setup j 9.02 on a Big Sur macos intel machine and get jconsole
and JHS running, but I've had no luck with JQT however. pacman downloaded
the binaries and I see them in the J bin directory but attempts to run JQT
don't even throw up - "you're doing it all wrong errors." I suspect macos
is attempting to protect me from running software Apple does not collect
royalties on.
I'm not a fan of the security obstacles current OSs are throwing up when it
comes to installing software! I was able to override the script blocks and
get the non JQT parts of J running but any advice from J users of recent
macos versions would be appreciated.
I'm really looking forward to setting up Linux virtual machines on this
thing ---- not!
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
