Mate, that is what I’m trying, but let me try again:
I haven’t checked, but i do believe you, it is for sure unmaintained. The maintainer providing packages, which isn’t correctly defines its dependencies. They are installable without JDK. Ergo: they are broken.
HaikuPorts doesn’t provides JDK currently, but the packages still have (!) to defines their dependencies. That’s what package management about is.
You are using an unmaintained repo and a broken packages. They definitely doesn’t working. The broken packages aren’t provided by Haiku or HaikuPorts. If Haiku would provide them, you should create a ticket at dev.haiku-os.org, if HaikuPorts would provide them, you should create an issue at HaikuPorts.
But neither Haiku nor HaikuPorts provides the broken packages, which makes headache you, so talk to your provider.
The provider, and ONLY the provider is responsible for the provided packages, and for their dependencies. But the dependencies could comes from different repo (like HaikuPorts).
The repo is unmaintained, you say. Sad, but if you care about the packages talk to the provider and try to get admin rights at the repo and fix the packages. In the meantime you could provide JDK in that repo too.
But it is neither Haiku nor HaikuPorts problem. I say that loud and clear. Please, read me.
The only Haiku related problem is the following: why the JDK is not available. But that’s a HaikuPorts problem, and while it is a problem, it is just tangential to the original post and problem. (I think there is already an issue about it at github with some explanation, have you checked it already?)
If JDK would be available at HaikuPorts, the packages from the 3rdparty repo would be still installable WITHOUT JDK, because they doesn’t defines JDK as a REQUIMENT.
And THIS is the problem, nothing else.
The packages are broken. Period.
I think, but i’m not responsible to decide it: we don’t care if you are newcomer or not. You have problem with packages? Sad to hear. Just talk to your provider. I cannot explain you better.
If you think it differently, explain, why should Haiku or HaikuPorts care about broken packages from an unmaintained repo with incorrect requiments.
The fact is: it is listed at the depot website just to to advertise 3rdparty repos. They aren’t activated default in Haiku, you activated them. From this moment who are responsible? You activated an unmaintained repo, so be prepared: problems will come.
I’m not rude, i’m not unfriendly, i just point the mistakes in your reasoning. And there are some.
It is NOT a Haiku/HaikuPorts problem.
Talk to your provider.