NixOS JVM | 120 Members | |
| 27 Servers |
| Sender | Message | Time |
|---|---|---|
| 19 Jul 2025 | ||
| Being able to host Exactly One minecraft server sucks | 20:35:54 | |
| Ok, but back to you original quesion: No, I don't neet a module configuration, just a pkgs configuration. But why were you asking? | 20:36:28 | |
| unfortunately the module system is kind of bad (my hot take) | 20:36:33 | |
| (but the things we do with the module system are nice) | 20:36:47 | |
| do wish we had something that didn't make singletons the happy path | 20:37:02 | |
| because manual containerization sucks | 20:37:10 | |
| Ok, so I'm now back where I started. Many alternatives, but none of which appears interesting of even feasible to me. So I'd like to add junixsocket. | 20:39:36 | |
| Crazy idea: What if we make junixsocket, perhaps just the two parts "junixsocket-common" and "junixsocket-native-common", a dependency on postgresql_jdbc? That way, every Nix package that uses pkgs.postgresql_jdbc would automatically have support for unix sockets. | 20:41:12 | |
| Not particularly crazy, a lot of packages do stuff like that, only skipping it if the optional dependency os extremely heavy | 20:41:57 | |
| * Not particularly crazy, a lot of packages do stuff like that, only skipping it if the optional dependency is extremely heavy | 20:42:15 | |
| So would it make sense if I propose a pull request for exactly that? Or would that be doomed to be rejected? (In which case I'd work on a less intrusive solution instead) | 20:43:03 | |
| Most PRs are usually doomed to inactivity instead of rejection | 20:43:37 | |
| This change makes perfect sense to me so I say go for it | 20:44:00 | |
| I'm a bit confused about java package conventions, though. So continuing my list of questions: | 21:32:58 | |
| 21:33:42 | |
3 .Java libraries are put into by-name/.../, contrary to what is usual in other languages within Nix (e.g. ocamlPackages, etc.). Should I follow that convention? | 21:34:59 | |
*
| 21:35:09 | |
| 21:46:34 | |
*
| 21:47:17 | |
In reply to @vog:matrix.orgJava libraries are a bit different because they aren't notably intertwined with each other, while languages like ocaml and python have a very intertwined library ecosystem | 21:55:35 | |
| Java libraries are treated by and large like normal packages both in Nix and elsewhere | 21:55:59 | |
In reply to @vog:matrix.orgAs far as I can tell javaPackages only has openjfx nowadays, and that will likely be moved out later on when separated from the jdk itself | 21:57:58 | |
| I was just curious and thought it might be good to have some context. | 22:55:05 | |
| Thanks! Regarding my last question, I decided to prefer fetchMavenArtifact, for the simple pragmatic reason that it allows me to easier reference to the sub libraries (junitsocket-common, etc.) separately. | 22:56:48 | |
| * Infinidoge 🏳️⚧️: Thanks for your responses! Regarding my last question, I decided to prefer fetchMavenArtifact, for the simple pragmatic reason that it allows me to easier reference to the sub libraries (junitsocket-common, etc.) separately. | 22:57:19 | |
| Makes sense to me | 22:57:32 | |
| 21 Jul 2025 | ||
| 15:50:24 | ||
| 22 Jul 2025 | ||
| Ok, I finally got around to create the PR. Please review! https://github.com/NixOS/nixpkgs/pull/427538 | 19:18:26 | |
| * Infinidoge 🏳️⚧️: Ok, I finally got around to create the PR. Please review! https://github.com/NixOS/nixpkgs/pull/427538 | 19:23:23 | |
| 23 Jul 2025 | ||
| 04:23:15 | ||