There should be no necessity to move anything into a templateVM. Never do that.
You can git clone and build the software in a dispvm, qvm-copy the compiled binary or package to your appVM and install it to /usr/local/bin/ inside your appVM. You can also consider to use bind-dirs inside your appVM.
I am not sure how to use bind-dirs. I was not a long-time Linux user before starting Qubes.
sdk list java
==== INTERNET NOT REACHABLE! ===================================================
Some functionality is disabled or only partially available.
If this persists, please enable the offline mode:
$ sdk offline
================================================================================
- currently in use
Does this mean I need to use a disp template and use bind-dirs?
I don’t know how this sdk tool works and if it’s possible to make it use proxy (or if proxy is supported by it at all).
It seems that sdkman install script is installing all files in user home directory so you can just install it in an app qube instead of a template. No need to use bind-dirs in this case.
It’s installing a new version of java so I can compile something. If I install it in the AppVM and compile in there, I’ll not have it in the template, which is what I want.
I really want to connect the template to the Internet.
A bit obtuse to the original question.
What about building Flatpaks for whichever App you desire?
Yes, you have to install the FlatPak manager to the Qube. Is the Flatpak manager Unsafe?
And I frankly do not have a sterile computer to compile Flatpaks (sterile-certain the resulting flatpaks compiled on it, are not corrupted.)
Plus. I have no experience compiling FlatPaks.
I do not trust Flatpaks, even from Flathub, to not be corrupted. So, yeah, I would have to compile on my own.
Try to set proxy environment variables before running sdk command:
export http_proxy=http://127.0.0.1:8082
export https_proxy=http://127.0.0.1:8082
sdk list java
