| 17 Jul 2025 |
 msgilligan | I'd like to make sure two things from this conversation are captured in GitHub Issues:
- The idea of using
jlink to add OpenJFX to Temurin. Which should allow Darwin to use Temurin rather than Zulu.
- Whatever technical details emily is explaining above that are not already covered by existing issues.
| 18:15:15 |
 emily | FWIW I haven't actually tried the jlink thing so I could be wrong about how it works :) | 18:18:30 |
| emily | feel free to open issues though | 18:18:41 |
| emily | I think in any case that it's likely not too hard to get OpenJFX building from source on Darwin even if jlink doesn't work. but I would really rather avoid building two JDKs in general | 18:18:57 |
| emily | it makes testing them a pain too | 18:19:02 |
| msgilligan | That's fine, I just want to make an issue to capture the idea, so someone can try it. | 18:19:09 |
| emily | I would prefer even avoiding the jlink thing but I don't understand Java modules enough to determine whether it's possible (other than telling people to get OpenJFX from Maven) | 18:19:23 |
| emily | I get the impression that nothing except OpenJFX actually uses them | 18:19:31 |
| msgilligan | I'm a big advocate of Java modules and I feel like I've been swimming upstream for the last 6 years. But the current is getting weaker and modules are beginning to be accepted. | 18:20:39 |
| msgilligan | OpenJFX made a bad decision to pretty much force modules on people and that's caused a lot of pain. | 18:20:57 |
| msgilligan | * OpenJFX made a bad decision to ~~pretty much~~ by default force modules on people and that's caused a lot of pain. | 18:21:33 |
| emily | I assume we can't do anything as simple as just JAVA_MODULES_PATH=${openjfx} to make existing builds that expect it to be built-in work. | 18:21:47 |
| msgilligan | * OpenJFX made a bad decision to pretty much by default force modules on people and that's caused a lot of pain. | 18:21:56 |
| emily | FWIW, while I sympathize with the overcommitted part (or I'd just have done all of this stuff already), I think you overestimate the skill level required to twiddle some flags until you get a new build error :) I expect nobody has even tried to build our OpenJDK source package on Darwin in a long time | 18:22:54 |
| msgilligan | I will try to take a look at it in a few weeks, if nobody else has. | 18:23:59 |
| msgilligan | I guess this issue is the one for building OpenJDK on Darwin: https://github.com/NixOS/nixpkgs/issues/313213 | 18:24:46 |
| msgilligan | * I will try to take a look at it in a few weeks September (or so), if nobody else has. | 18:42:59 |
| msgilligan | I'm not sure what assigning yourself on Issue on GitHub means to the Nixpkgs community, but I've started using it to mean "I am interested in contributing to this when I can". Will that confuse or upset anyone? | 18:44:42 |
 Infinidoge 🏳️⚧️ | I've always seen it as "$X is working on this", with varying definitions of 'working on' | 18:45:23 |
| msgilligan | Does "thinking about it" count? 🤣 | 18:46:06 |
| emily | I don't think it gets used that much honestly | 18:47:47 |
| emily | so you can probably assign whatever semantics you want | 18:47:52 |
| emily | but I would say that it will make someone else less likely to pick it up, because "someone else is already on it" | 18:48:03 |
| emily | so if you'd rather invite someone else to take it up and don't plan to get to it any time soon, then maybe skip the assignment | 18:48:15 |
| msgilligan | I don't want to discourage anyone! Good point. | 18:50:16 |
| msgilligan | I wish there was a way to mark an issue as "I'd like to help". i.e. one step beyond giving it a 👍 | 18:51:27 |
| emily | you can just comment :) | 18:52:09 |
| msgilligan | I do that. But it would be nice to be able to find all the issues I'm interested in helping on with a search on GitHub. | 18:53:44 |
| msgilligan | Like a bookmark or something | 18:54:01 |
| Infinidoge 🏳️⚧️ | Subscribe to the issue, then you can bookmark it from notifications | 18:54:28 |
