On Sat, 05 Oct 2024 12:24:34 +0200,
Klemens Nanni <kn@openbsd.org> wrote:
> 
> 05.10.2024 00:40, Kirill A. Korinsky пишет:
> > @@ -121,6 +121,8 @@ libexec/visualvm/platform/modules/lib/i3
> >  libexec/visualvm/platform/modules/lib/i386/linux/
> >  libexec/visualvm/platform/modules/lib/i386/linux/libjnidispatch-nb.so
> >  libexec/visualvm/platform/modules/lib/libflatlaf-linux-x86_64.so
> > +libexec/visualvm/platform/modules/lib/libflatlaf-macos-arm64.dylib
> > +libexec/visualvm/platform/modules/lib/libflatlaf-macos-x86_64.dylib
> >  libexec/visualvm/platform/modules/lib/riscv64/
> >  libexec/visualvm/platform/modules/lib/riscv64/linux/
> >  libexec/visualvm/platform/modules/lib/riscv64/linux/libjnidispatch-nb.so
> There are a bunch of arch- and/or os-specific files in PLIST.
> Are they really used on OpenBSD or do we package every supported platform
> for nothing?

Well.. I had tried to remove it, and visualvm complience on start like that

  WARNING [org.graalvm.visualvm.lib.profiler.NetBeansProfiler]: Failed to initialize the Profiler engine: Problem with a required JFluid installation directory or file /usr/local/libexec/visualvm/visualvm/lib/deployed/jdk16/solaris

seems that is is required somehow.

-- 
wbr, Kirill