Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 815433 - www-client/firefox pure wayland ebuild
Summary: www-client/firefox pure wayland ebuild
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-30 09:53 UTC by Cedric Sodhi
Modified: 2022-06-01 18:16 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Sodhi 2021-09-30 09:53:23 UTC
To my knowledge, as of 90 (?), Firefox can canonically be build for pure wayland, but the current ebuild is still wired to X11; among others:

> x11-libs/libX11       
> x11-libs/libXcomposite
> x11-libs/libXdamage   
> x11-libs/libXext      
> x11-libs/libXfixes    
> x11-libs/libXrender
> >=x11-libs/cairo-1.10[X]  
> >=x11-libs/gtk+-3.4.0:3[X]
Comment 1 Thomas Deutschmann (RETIRED) gentoo-dev 2021-09-30 18:53:31 UTC
Sadly, that's not the case. I recommend that you create a chroot, satisfy all deps (emerge -a1 --onlydeps firefox), then remove these packages (emerge -C ...) and just try to build firefox (ebuild firefox-92...ebuild clean install). You will notice that configure will already fail.
Comment 2 Joonas Niilola gentoo-dev 2021-10-02 06:04:24 UTC
Related:
https://mastransky.wordpress.com/2021/10/01/firefox-wayland-development-in-2021/

So let's look at this after 96 again.
Comment 3 Cedric Sodhi 2022-06-01 18:02:59 UTC
101 builds without X11 libs, although the binary release is currently not configured for that. Any chance we could patch this depending on the USE flags?
Comment 4 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-06-01 18:16:04 UTC
(In reply to Cedric Sodhi from comment #3)
> 101 builds without X11 libs, although the binary release is currently not
> configured for that. Any chance we could patch this depending on the USE
> flags?

Let's keep discussion of that in bug 848858.