Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #12624

Packaging applications with JVM version restrictions

Show all headers | View raw

Is there Is there a policy or preferred way to handle a package that
needs a particular version or versions of java?  e.g. say it doesn't
work with < 9.

I could imagine it might not want to just rely on /usr/bin/java because
you might not want it to break if the system has 8 and 11 installed, and
then the local admin changes the default to 8 via update-alternatives.

To avoid that, I imagine the application's /usr/bin/something could
examine $(update-alternatives --list java) to find a suitable version,
but is that reasonable, or is there a preferable approach?

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Back to linux.debian.maint.java | Previous | Next — Next in thread | Find similar

Thread

Packaging applications with JVM version restrictions Rob Browning <rlb@defaultvalue.org> - 2023-04-17 21:50 +0200
  Re: Packaging applications with JVM version restrictions Thorsten Glaser <t.glaser@tarent.de> - 2023-04-17 22:00 +0200
    Re: Packaging applications with JVM version restrictions Loïc Rouchon <loic@loicrouchon.com> - 2023-04-18 15:30 +0200
      Re: Packaging applications with JVM version restrictions Thorsten Glaser <t.glaser@tarent.de> - 2023-04-19 09:20 +0200
        Re: Packaging applications with JVM version restrictions Loïc Rouchon <loic@loicrouchon.com> - 2023-04-19 12:10 +0200
          Re: Packaging applications with JVM version restrictions gregor herrmann <gregoa@debian.org> - 2023-04-20 20:00 +0200
            Re: Packaging applications with JVM version restrictions Loïc Rouchon <loic@loicrouchon.com> - 2023-05-06 15:40 +0200

csiph-web