Re: lang/openjdk-bin for platforms other than amd64 NetBSD or Linux?

["J. Lewis Muir" <jlmuir%imca-cat.org@localhost>]

On 03/02, Greg Troxel wrote:
> "J. Lewis Muir" <jlmuir%imca-cat.org@localhost> writes:
> > My use case is that I want to build binary packages for Linux, macOS,
> > and NetBSD, and I want to package package A for pkgsrc that depends on
> > Java, and I want the Java dependency from package A to be satisfied from
> > pkgsrc, not the underlying OS, so that I can build binary packages on a
> > minimal system of each platform and know that installing binary package
> > A will result in an appropriate JRE (Java Runtime Environment) getting
> > installed so that package A will work.
> 
> I don't see how it follows that you want openjdk-bin, but I'm guessing
> that either:
>   - you need 21 not 17, and openjdk21 doesn't build on some platforms.

Yes, this one.  Sorry I wasn't too clear on that.  There's no
lang/openjdk21 binary package for macOS arm64 from MNX.  It's marked
with a build status of "prefailed" at

  https://releng.netbsd.org/bulktracker/pkg/46287274

> We generally do not encode dependencies on foo-bin; instead there's a
> way to see we need a foo and satisfy it multiple ways.  Sometimes this
> is based on what's installed, and sometimes it's like RUST_TYPE.  
 
OK, thanks for the clarification on that.  I was aware that this
fallback mechanism existed, but I wasn't aware that you generally do not
encode a dependency on foo-bin.

> > I'm also aware of lang/openjdk21, but it has a big scary warning in
> > DESCR that says the following:
> >
> >   This package is NOT certified to be compatible with any Java standard.
> >   Use at own risk.
> 
> Well, nothing is certified in pkgsrc, in general.  I wouldn't take that
> too seriously, but rather ask "Has anyone found that the openjdk21
> package does the wrong thing?"

Well, if the maintainer thinks it should be fine, then I'd say the
warning should just be removed, and then I wouldn't have reason to doubt
the package in the first place and ask that question.  It seems to me
that the warning will scare people away and make them not use it.  I
mean, are there similar warnings for other pkgsrc language builds like
Python, Ruby, Rust, Go, or whatever?  Or maybe those projects don't
have an equivalent thing (i.e., a Technology Compatibility Kit)?  They
probably all have a test suite, though.  But I doubt the DESCR file
for any of them has anything about whether the test suite passes or
not.  If that's the case, then it seems like Java shouldn't be treated
any differently than those.  I don't know anything about lang/openjdk21
other than that the Makefile looks somewhat complex.  And when I see a
warning like that but don't see a similar warning for other languages,
it makes we wonder what's wrong with it.

Lewis