textproc/opensearch update 3.1.0 -> 3.2.0

[admin_hackacad.net]

Summary

textproc/opensearch: Update to 3.2.0

Changelogs:

https://github.com/opensearch-project/OpenSearch/releases/tag/3.2.0

Add opensearch_flags for temporary startup parameters
Add opensearch_env for setting environment variables
Add proper check for aarch64
Allow only amd64 and aarch64
Remove AVX2 check

[vvd]

Bump OpenJDK to upstream supported version 24

Is this the minimum upstream supported version of Java?

[admin_hackacad.net]

approved by opensearch@

[admin_hackacad.net]

In D52392#1201249, @vvd wrote:

Bump OpenJDK to upstream supported version 24

Is this the minimum upstream supported version of Java?

Supported JAVA is 11+ (https://docs.opensearch.org/latest/install-and-configure/install-opensearch/index/)
The bundled version is 24.
I decided to bump Java to the upstream 24(+) as there are major improvements on machines with large amount of memory.
https://reviews.freebsd.org/D52354

[vvd]

Version 21 is LTS, version 24 is not.
The recently released version 25 is also LTS, but it's not yet available in ports.
I wouldn't specify a non-LTS version unless absolutely necessary.

[vvd]

The bad thing is that the ports framework does not support version prioritization, but only a set that will be sorted and the minimum possible version will be selected for binary packages.

[admin_hackacad.net]

In D52392#1201468, @vvd wrote:

The bad thing is that the ports framework does not support version prioritization, but only a set that will be sorted and the minimum possible version will be selected for binary packages.

LTS is a very good point.

I'd prefere:
SUPPORTED_JAVA=11≤x≤24
DEFAULT_JAVA=24

[admin_hackacad.net]

rollback
JAVA_VERSION=21

[vvd]

I think we need something like this:
USES=java:min=11,max=24,recommended=21
min and max same as for USES=llvm, but recommended not implemented anywhere.
Instead of current:
USES=java
JAVA_VERSION=21+
But someone needs to implement this.

[admin_hackacad.net]

Approved by opensearch@

[vvd]

Where is OPENSEARCH_ARCH variable used?

Suggestion:
OPENSEARCH_ARCH= ${ARCH:S|aarch64|arm64|:S|amd64|x64|}

[admin_hackacad.net]

Approved by opensearch@

In D52392#1205895, @vvd wrote:

Where is OPENSEARCH_ARCH variable used?

Suggestion:
OPENSEARCH_ARCH= ${ARCH:S|aarch64|arm64|:S|amd64|x64|}

Fixed this. Arch is used for downloading the corresponding tar ball.

[vvd]

In D52392#1206146, @admin_hackacad.net wrote:

Approved by opensearch@

In D52392#1205895, @vvd wrote:

Where is OPENSEARCH_ARCH variable used?

Suggestion:
OPENSEARCH_ARCH= ${ARCH:S|aarch64|arm64|:S|amd64|x64|}

Fixed this. Arch is used for downloading the corresponding tar ball.

Then distinfo should also contain opensearch-3.2.0-linux-arm64.tar.gz.

Also, why wouldn't you want to use the "short" version of the OPENSEARCH_ARCH definition?