unify the use of +threads as a variant name

[mojca (Mojca Miklavec)]

From #43593: would it make sense to unify the variant names used across different ports?

Here are some variant names from different ports:

boost:     variant no_single  description {Disable building single-threaded libraries}
gauche:    variant no_threads { configure.args-delete --enable-threads=pthreads }
raxml:     variant pthreads   conflicts hybrid description {Pthreads implementation}
cherokee:  variant no_pthread description {Disable threading support}

sbcl:      variant threads    description {Enable multi-threaded runtime using the Mach pthreads interface.}
tcl:       variant threads    description {add multithreading support}
yap:       variant threads
abinit:    variant threads    description {Build with support for multi-thread support (openMP)}
openmpi:   variant threads    description {enable threads for MPI applications}
wannier90: variant threads    description {Build with threaded ATLAS}

hdf5:      variant threadsafe description {Enable threadsafety (experimental, fails unit-tests)}
hdf5-18:   variant threadsafe description {Enable threadsafety. +threadsafe is EXPERIMENTAL with +cxx, +fortran, or any mpi variant}

If this doesn't apply to your port (that is: if the keyword +threads misses the point – I'm not sure if +threads and +threadsafe have "compatible" meanings for example), please say so and remove your port from the list of affected ports. But variants like +no_threads should certainly be inverted.

[mf2k (Frank Schima)]

Adding hdf5-18 and Cc'ing the maintainer for possible comment.

[mamoll (Mark Moll)]

Thread safety is different from multi-threaded. Thread-safe code can be used in multi-threaded code, but isn't necessarily multi-threaded itself. Multi-threaded code necessarily must be thread-safe. Nevertheless, I can see the value in having fewer variant names. It'd be nice if a multi-threaded port that depended on hdf-18 would build the threadsafe variant of hdf5-18. That is more likely to happen if the hdf5-18 variant is named "threads". In other words, I'd be okay with this change, as long as the variant description is clear what it means in each case.

[mf2k (Frank Schima)]

Removing former maintainer from Cc. See #43692.

[petrrr]

Removing hdf5-18 again. It has become as stub w/o variants and can to be removed in few days.

[mf2k (Frank Schima)]

Updating maintainers in Cc list

[mf2k (Frank Schima)]

See #58384.

[michaelld (Michael Dickens)]

OK. So for "boost" by default we install just the multi-threaded version (suffix "-mt"). IIRC, disabling the default "+no_single" will then -also- build a single-threaded version (suffix "-st") ... completely different ABI files. I don't see how "+threads" is relevant here.

[herbygillot (Herby Gillot)]

In daed60864683925cef2999bfe3bcadbab25039fe/macports-ports (master):

cherokee: update to 1.2.204

• use distfiles from Github as official site points to Github-hosted assets
• use recommended checksum types
• patch and configure to use $prefix/var/www as www root
• remove all variants, add new variants for ffmpeg and LDAP
• add Python 2.7 as lib dependency, also needed for build process
• use automake/autoconf/libtool in build process

Closes: #30324
Closes: #33768
Closes: #44766
See: #33767
See: #43704