From b3bfc7186e4f820493aa2eb8cc65f0efba7ed6f6 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Mon, 4 Dec 2023 23:01:41 +0000 Subject: gentoo auto-resync : 04:12:2023 - 23:01:41 --- profiles/Manifest.gz | Bin 186226 -> 186229 bytes profiles/base/package.use.force | 15 +++++++++------ 2 files changed, 9 insertions(+), 6 deletions(-) (limited to 'profiles') diff --git a/profiles/Manifest.gz b/profiles/Manifest.gz index 4e3ffc09188b..181cf1e60b8c 100644 Binary files a/profiles/Manifest.gz and b/profiles/Manifest.gz differ diff --git a/profiles/base/package.use.force b/profiles/base/package.use.force index 900a336bfd2b..2edf7a848549 100644 --- a/profiles/base/package.use.force +++ b/profiles/base/package.use.force @@ -8,12 +8,15 @@ # confirmation emails when I try to sign up. =sci-mathematics/giac-1.9.0.67 gui -# Matt Turner (2023-09-18) -# Disabling gstreamer seems to be untested upstream and is often broken. -# The gstreamer dependencies are trivial in compile time and disk usage -# compared to webkit-gtk. -# Bugs #911663, #914362 ->=net-libs/webkit-gtk-2.42 gstreamer +# Michael Orlitzky (2023-12-04) +# This was originally forced because gstreamer-less builds are untested +# upstream and are often broken (e.g. bugs 911663 and 914362). But from +# the user's perspective, having it forced is worse than having it fail +# to build; if it fails, you can always set USE=gstreamer for one +# version, i.e. at least you have a choice. The two latest 2.42.x +# ebuilds in the tree both build fine with gstreamer disabled, so it is +# at least safe to re-enable for those. Older ebuilds, who knows. + (2023-08-14) # OpenMW is only playtested with LuaJIT, and in fact unit tests fail with Lua-5. -- cgit v1.2.3