hdf5: Fix build with Sonoma/CLT 15.0

[Dave-Allured]

Description

• Remove -commons from configure, not supported in Sonoma/CLT 15.0.
• -commons no longer needed for HDF5 series 10.0 and later.

Closes: https://trac.macports.org/ticket/68194
Was fixed upstream: HDFGroup/hdf5#3581

Type(s)

• bugfix
• enhancement
• security fix

Tested on

CI only
macOS 11, 12, 13, x86_64 only

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL?
• checked your Portfile with port lint --nitpick?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@eborisch for port hdf5.

[reneeotten]

there should be only one commit for this; instead of adding mew ones when making a change, please amend the original commit instead.

[reneeotten]

please add a link jn fhe patchfile to the upstream commit/PR

[Dave-Allured]

Done. See corrected PR #20572.

[ryandesign]

Was fixed upstream: HDFGroup/hdf5#3581

Was submitted to upstream but has not yet been accepted.

there should be only one commit for this; instead of adding mew ones when making a change, please amend the original commit instead.

It's no problem for us to fix this when merging, by using the "Squash and merge" button and rewriting the commit message.

[reneeotten]

It's no problem for us to fix this when merging, by using the "Squash and merge" button and rewriting the commit message.

Sure, everything can be fixed but ideally regular contributors should be aware of this and take of it themselves.

[Dave-Allured]

It's no problem for us to fix this when merging, by using the "Squash and merge" button and rewriting the commit message.

Sure, everything can be fixed but ideally regular contributors should be aware of this and take of it themselves.

Agreed. However, github.com does not provide normal squash or merge capability, and I am avoiding git for security. The best I can do is to move to a new branch, and make a single, cleaned-up commit.

[Dave-Allured]

The best I can do is to move to a new branch, and make a single, cleaned-up commit.

Um, github.com does not support files in more than one directory in a single commit. I will have to make one commit for the portfile, and another for the patch file.