Retrospective of my term as a Director for the GNOME Foundation
On the spring 2024 I presented my candidature, and eventually got elected for the Board of Directors at the GNOME Foundation. Directors are elected democratically by the GNOME Foundation members,...pabloyoyoista (GNOME adventures in mobile)
Doughnut Lollipop 【記録係】
in reply to feld • • •feld
in reply to Doughnut Lollipop 【記録係】 • • •Doughnut Lollipop 【記録係】
in reply to feld • • •feld
in reply to Doughnut Lollipop 【記録係】 • • •feld
in reply to feld • • •turns out you can't use -Dos.name=Linux to trick Java into changing this value.
You also can't use a custom Java Agent. I made one, used it like -javaagent:osagent.jar=Linux to let me inject a different value into the JVM.
Turns out when you do that, Java kinda explodes. Linux-specific things are not in the FreeBSD JVM so it breaks.
When something relies on matching the os.name, the only thing you can do is modify the Java jar/class bytecode directly so the JVM doesn't blow up.
Super annoying because I thought I had a really clever solution to avoid needing to repeat this process every time the software is updated.
Guido Kollerie
in reply to feld • • •feld
in reply to Guido Kollerie • • •@guido @ronnie_bonkers Now that it's working (with unknown missing functionality), keeping it working isn't too hard. One manual step every new controller release to modify a jar before publishing the port update isn't too bad.
I really just don't want to be forced to run a VM for this 🤮