public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Hoshino Lina <lina@lina.yt>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: Move core BRs out of GTK4 section & add missing ones
Date: Fri, 07 Aug 2026 16:08:35 GMT	[thread overview]
Message-ID: <178611891509.1.12335069333945681851.rpms-chromium-fa8417855561@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/chromium
            Branch : epel9-next
            Commit : fa84178555617e070365ee581cf4c470984609c9
            Author : Hoshino Lina <lina@lina.yt>
            Date   : 2025-12-13T14:55:06+09:00
            Stats  : +11/-4 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/chromium/c/fa84178555617e070365ee581cf4c470984609c9?branch=epel9-next

            Log:
            Move core BRs out of GTK4 section & add missing ones

These BRs are required by Chromium proper, even when built without any toolkits
(e.g. as CEF).

Add a few missing ones (wayland-devel, xkbcommon, pangocairo) and move others
out of the GTK4 conditional, since they aren't actually related to GTK4, they
just happened to be pulled in by gtk3-devel.

---
diff --git a/chromium.spec b/chromium.spec
index 472ec62..a659713 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -769,10 +769,6 @@ BuildRequires:	opus-devel
 BuildRequires: %{chromium_pybin}
 %if %{gtk_version} == 4
 BuildRequires: pkgconfig(gtk4)
-BuildRequires: pkgconfig(xrandr)
-BuildRequires: pkgconfig(atspi-2)
-BuildRequires: pkgconfig(atk-bridge-2.0)
-BuildRequires: pkgconfig(xcomposite)
 BuildRequires: pkgconfig(xcursor)
 BuildRequires: pkgconfig(xi)
 BuildRequires: pkgconfig(xrender)
@@ -789,6 +785,17 @@ BuildRequires: pkgconfig(gtk+-3.0)
 # GTK modules it expects to find for some reason.
 Requires: libcanberra-gtk3%{_isa}
 %endif
+
+# Build deps of Chromium proper which are often transitively pulled in by toolkits (GTK, Qt),
+# but are still required without them.
+BuildRequires: pkgconfig(atspi-2)
+BuildRequires: pkgconfig(atk-bridge-2.0)
+BuildRequires: pkgconfig(pangocairo)
+BuildRequires: pkgconfig(xkbcommon)
+BuildRequires: pkgconfig(xcomposite)
+BuildRequires: pkgconfig(xrandr)
+BuildRequires: wayland-devel
+
 %if ! %{bundlepylibs}
 %if 0%{?fedora} || 0%{?rhel} >= 8
 BuildRequires: python3-jinja2

                 reply	other threads:[~2026-08-07 16:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178611891509.1.12335069333945681851.rpms-chromium-fa8417855561@fedoraproject.org \
    --to=lina@lina.yt \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox