My impulse would be to decide which distros we want to officially support, and 
provide packages for them. Perhaps Arch, Debian, and Ubuntu? Both installers 
for Linux applications and compiling Java to native code strike me as odd 
approaches that go against the grain of usual software installation, and while 
I'm not opposed to having them as options for distros we don't have packages 
for, it does seem liable to increase our support load.

Providing packages would allow giving upgrades some nice properties as well - 
instead of having to write upgrade logic ourselves, the package manager can do 
it. We need only (expose and) add a package repo like the Google Chrome package 
does by default. A tool to mirror a USK to disk would be useful here; if memory 
serves I've written up ideas about this in the past.


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, April 12, 2019 4:31 PM, Arne Babenhauserheide <arne_...@web.de> 
wrote:

> Hi,
>
> With Java 11 Webstart is no longer part of the official
> distribution. JNLP files no longer start by default.
>
> What do you think about just providing the jar?
>
> Or should we try whether we can get the installer compiled with Graal?
> https://www.graalvm.org/docs/getting-started/#native-images
>
> Best wishes,
> Arne
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken

Reply via email to