NixOS JVM | 121 Members | |
| 27 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 Jul 2025 | ||
| You've been doing a lot of legwork recently, and there is no reason to be particularly choosy about who gets pinged, Anyone who wants to sign up for the Sisyphean task can have in aa for as I'm concerned | 06:16:19 | |
| * You've been doing a lot of legwork recently, and there is no reason to be particularly choosy about who gets pinged, Anyone who wants to sign up for the Sisyphean task can have in as for as I'm concerned | 06:16:30 | |
| That and I happen to be in BST and awake early | 06:16:45 | |
| British Summer TIme? | 06:18:59 | |
| Yeah | 06:19:09 | |
| Vacation right? You're US-based I thought. | 06:19:32 | |
| Last day on my family's Scotland trip, flying back today | 06:19:37 | |
| Nice! | 06:19:51 | |
| Here's my preliminary work on a Nix JDK Package Dashboard:
| 06:34:53 | |
graalvmPackages.graalvm-ce, graalvmPackages.graalvm-oracle, and jetbrains.jdk are currently commented out because I'm not handling sub-packages yet. | 06:36:31 | |
| Makes sense, looks good so far Could look for the recurse for derivations flag | 06:37:50 | |
| (Unsure how much you're doing in Nix vs shell) | 06:38:33 | |
| 06:38:54 | |
| This is totally uncharted territory for me. | 06:39:38 | |
| Wondering if I should create an issue and/or a draft PR. I think the issue might be a good place to discuss requirements and features in a way that can get people involved. | 06:41:55 | |
| I was thinking it might make sense to define some kind of JDK specific metadata that could live in the root directory of each JDK package-set. | 06:42:47 | |
For example, I currently have definitions of which versions are supposed to be supported by each JDK and whether their is a default (e.g. corretto doesn't exist, but zulu defaults to zulu21. | 06:45:41 | |
* For example, I currently have definitions of which versions are supposed to be supported by each JDK and whether there is a default (e.g. corretto doesn't exist, but zulu defaults to zulu21. | 06:46:00 | |
* For example, I currently have definitions of which versions are supposed to be supported by each JDK and whether there is a default (e.g. corretto doesn't exist, but zulu defaults to zulu21.) | 06:46:12 | |
| I'd rather have a list of JDK root paths and query them for metadata (perhaps with defaults for package-sets that haven't implemented the metadata yet) | 06:48:05 | |
I don't know what this means. | 06:48:31 | |
Currently jdk-dashboard.nix and jdk-dashboard.sh are in nixpkgs/maintainers/scripts but I'm not sure that is the right place. | 06:49:59 | |
In reply to @msgilligan:matrix.orgGenerally on sets of packages, there is a specific attr (I forget which exactly) that is set to true to flag that functions should look through the attribute set for derivations | 06:51:18 | |
| e.g.
and
| 06:51:34 | |
| I believe there should be more info attached to lib.recurseIntoAttrs | 06:51:37 | |
and I'm including - and _ as a prefix in some versions as there is currently no consistent mechanism for concatenating name to version. e.g. zulu21, but temurin-bin-21 and graalvmPackages.graalvm-oracle_17 | 06:54:17 | |
| We should probably look at what SDKMAN! does: https://sdkman.io/jdks | 07:18:07 | |
| Note that they are using Temurin as their default JDK. | 07:18:27 | |
| And of course, what I would like to be able to do is to view the versions of each Nixpkgs JDK and display it next to the latest version available for that JDK. We have updaters for some of the JDKs that will pull the latest versions from a server. | 07:42:33 | |
| It looks like there is an API that can give that info for many distributions: https://github.com/foojayio/discoapi | 07:43:14 | |