Upstream uses release mode only for behavior tests, full suite is run
primarily with Debug, so other modes tend to fail with strange errors.
Seems like no other distro runs them in different modes, so align it
with upstream and everyone else.
Also restore `RESTRICT=test` for LLVM-disabled builds; it was removed
by mistake in some previous commit.
Bug: https://bugs.gentoo.org/949878
Signed-off-by: Eric Joldasov <bratishkaerik@landless-city.net>
Closes: https://github.com/gentoo/gentoo/pull/40891
Signed-off-by: Sam James <sam@gentoo.org>
- currently just for 136 (rapid),
- initial version that still provides a working browser with a smooth
experience - avoiding any (hardcore) hardening for now - users are
encouraged to study and cherry-pick their own configs from arkenfox/user.js,
- while "-telemetry" should be sufficient enough on its own disabling lots of
telemetry functionality from the build system, go through some related
telemetry settings from arkenfox/user.js and include more of them here just
in case.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
I'd got confused by the tight dep in old lo-bin and assumed that was
to do with how we were building it, but that wasn't right in the end.
Bug: https://bugs.gentoo.org/950497
Signed-off-by: Sam James <sam@gentoo.org>
In fbd7f2ebe1, when I fixed a typo, I made
a problem far worse (as reported at https://forums.gentoo.org/viewtopic-t-1172908.html).
The GNOME integration also contains the GTK(3) VCL, which means that
deleting it (with USE=-gnome, which became far more common than USE=-java
as before w/ the typo) leaves us with only the ugly fallback backend.
Now, in looking into this, I realised that the KDE integration also installs
a Qt 5 VCL, but let's continue to remove that for now at least given adding
new Qt 5 at this point isn't desirable.
Bug: https://bugs.gentoo.org/950393
Signed-off-by: Sam James <sam@gentoo.org>
... for the following in firewall-applet:
```
import gi
gi.require_version("Notify", "0.7")
from gi.repository import Notify
```
Reported on IRC by trashboat.
Signed-off-by: Sam James <sam@gentoo.org>
- >=2.71 will work ("latest" is the default), while the WANT_AUTOCONF line
will always pull 2.71 exactly and that's unnecessary.
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
Merging with the other cstdint patch to re-use the description.
Believe 6.9 patchset is missing 1 bit of that patch that I forgot
about when rebasing it, but will update the patchset for 6.9.0-rc
later rather than make a separate patch here.
Closes: https://bugs.gentoo.org/950579
Thanks-to: Anthony G. Basile <blueness@gentoo.org>
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
- add a patch that's currently being worked upstream which fixes runtime
issues when compiled with gcc and lto,
- handle rust-simd by enabling it on supported arches, so unkeyworded arches
can probably compile the browser with --disable-rust-simd by default
without editing the ebuild,
- sync the updated configure option from rapid to esr
(system-ffi, update-channel).
- while "permissions.manager.remote.enabled" is disabled through the default
pref settings, the setting will actually only be active in the rapid (136)
version.
Bug: https://bugs.gentoo.org/950229
Signed-off-by: Joonas Niilola <juippis@gentoo.org>