Bug 286203 was stupid. USE=threads doesn't do threaded compression or decompression, much to my disappointment. It makes liblzma threadsafe. configure.ac says AC_ARG_ENABLE([threads], AC_HELP_STRING([--disable-threads], [Disable threading support. This makes some things thread-unsafe.]), [], [enable_threads=yes]) This flag either needs to be renamed to threadsafe or removed and turned on always.
seems to me that existing usage falls under the preview of USE=threads, as does future usage (once threaded compress/decompress is added to the tools)
(In reply to comment #1) > seems to me that existing usage falls under the preview of USE=threads, as > does future usage (once threaded compress/decompress is added to the tools) I don't think we have any precedent for USE flags for things that are planned to be implemented.
tend to agree w/ matts; do we really have any justification in this day/age to have non-threadsafe as an option? Aka, what's the actual hit?
i certainly like being able to disable threads for embedded systems i'd also point out that the ebuild is IUSE=+threads, so only people turning off USE flags will run into a problem and i have no sympathy for them
commit 0c5a1376faafca0e8cac8d072a1ae6afb240af21 Author: David Seifert <soap@gentoo.org> Date: Sat Jul 17 00:10:40 2021 +0200 app-arch/xz-utils: enable threads unconditionally * fedora/debian/arch all enable threads unconditionally Signed-off-by: David Seifert <soap@gentoo.org>
