Will try to keep older versions around in future but had to rename
a few of the files due to error in script (contents are fine,
just dates were a week wrong).
Signed-off-by: Sam James <sam@gentoo.org>
USE=threads is a terrible USE flag (not the fault of net-misc/curl
or its maintainer) and we're looking to get rid of it entirely.
This is motivated further by the fact users have USE=threads
in make.conf seeking performance improvements and such (which is understandable)
but as per below, it can lead to conflicting and inconsistent effects.
(In particular, anyone with USE="threads" in make.conf (don't do this
for the reasons below!) will end up with a REQUIRED_USE issue between
the now-default USE=adns and USE=threads).
There are a few possibilities with threads support:
1. Upstreams always have threads support (hence USE=threads is only affecting
a "handful" of packages anyway, not every single package, as many will just
always be using pthreads and there's no way of disabling it);
2. The "threads" toggle means enabling some experimental or legacy implementation
(think e.g. dev-lang/perl, which uses USE=ithreads for this, as it breaks ABI)
(also applies to net-misc/curl given USE=threads doesn't help with the adns
functionality many applications desire, see linked bug);
3. Not having "threads" on enables some experimental or legacy implementation again
(this *again* applies to net-misc/curl given USE="-adns -threads" leaves
us with a dodgy implementation as well).
Commit 60b7aaa7a7 enabled adns by default
(IUSE=+adns).
This commit drops USE=threads entirely and makes the default pthreads with
adns opt-in with IUSE=+adns still.
Now, the ebuild previously had REQUIRED_USE="threads? ( !adns )". I can't
see a reason for this other than making the previous situation "meaningful",
i.e. allowing people to decisively choose which is used at runtime, as
while curl can build with both threads and adns, I think adns ends up
preferred at runtime.
With this change and given all of the above, we actually want adns to
take priority if it's set, as threads will just be the default, so
drop the REQUIRED_USE.
Bug: https://bugs.gentoo.org/699632
See: 60b7aaa7a7
Signed-off-by: Sam James <sam@gentoo.org>
Closes: https://github.com/gentoo/gentoo/pull/27111
Signed-off-by: Sam James <sam@gentoo.org>
Had a rocky start with egl-wayland, but no known issues anymore,
and is a production branch. 510 branch on the other hand is getting
behind fixes and will ultimately be removed (no known reasons to
use over 515).
Was tempted to mask kernel-open in stable, but it already comes with
several warnings and would rather not complicate things for users
that want to try it.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>