public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libheif] epel10: Add a bootstrap build path to break a glycin-related dep loop
Date: Thu, 30 Jul 2026 20:23:25 GMT	[thread overview]
Message-ID: <178544300579.1.548703855333497447.rpms-libheif-e740e76b5b1b@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/libheif
            Branch : epel10
            Commit : e740e76b5b1b0589d4c33246a27db233fc46ba10
            Author : Adam Williamson <awilliam@redhat.com>
            Date   : 2025-09-06T10:32:50-07:00
            Stats  : +26/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/libheif/c/e740e76b5b1b0589d4c33246a27db233fc46ba10?branch=epel10

            Log:
            Add a bootstrap build path to break a glycin-related dep loop

The recent glycin / gdk-pixbuf2 changes introduce two paths by
which a regular build of libheif buildrequires itself - one via
sdl2-compat-devel, the other via gdk-pixbuf2-devel. This adds a
bootstrap build path which disables both of those, to allow for
initial builds and rebuilds for dependency bumps.

---
diff --git a/libheif.spec b/libheif.spec
index af4c7c0..b8331b9 100644
--- a/libheif.spec
+++ b/libheif.spec
@@ -1,4 +1,23 @@
 %global somajor 1
+# this is used for breaking a self-dependency on build, via
+# two paths, first:
+# libheif BuildRequires: pkgconfig(sdl2) == sdl2-compat-devel
+# sdl2-compat-devel -> sdl2-compat
+# sdl2-compat -> SDL3
+# SDL3 -> libdecor
+# libdecor -> gtk3
+# gtk3 -> gtk-update-icon-cache
+# gtk-update-icon-cache -> gdk-pixbuf2
+# gdk-pixbuf2 -> glycin-libs
+# glycin-libs -> glycin-loaders
+# glycin-loaders -> libheif
+# second:
+# heif-pixbuf-loader BuildRequires: pkgconfig(gdk-pixbuf-2.0) == gdk-pixbuf2-devel
+# gdk-pixbuf2-devel -> gdk-pixbuf2
+# gdk-pixbuf2 -> glycin-libs
+# glycin-libs -> glycin-loaders
+# glycin-loaders -> libheif
+%bcond bootstrap 1
 
 Name:           libheif
 Version:        1.20.1
@@ -20,7 +39,9 @@ BuildRequires:  pkgconfig(libjpeg)
 BuildRequires:  pkgconfig(libopenjp2)
 BuildRequires:  pkgconfig(libpng)
 BuildRequires:  pkgconfig(openh264)
+%if !%{with bootstrap}
 BuildRequires:  pkgconfig(sdl2)
+%endif
 BuildRequires:  pkgconfig(zlib)
 %ifnarch %{ix86}
 BuildRequires:  pkgconfig(openjph) >= 0.18.0
@@ -43,6 +64,7 @@ file format decoder and encoder.
 
 # ----------------------------------------------------------------------
 
+%if !%{with bootstrap}
 %package -n     heif-pixbuf-loader
 Summary:        HEIF image loader for GTK+ applications
 BuildRequires:  pkgconfig(gdk-pixbuf-2.0)
@@ -54,6 +76,7 @@ This package provides a plugin to load HEIF files in GTK+ applications.
 
 %files -n heif-pixbuf-loader
 %{_libdir}/gdk-pixbuf-2.0/*/loaders/libpixbufloader-heif.so
+%endif
 
 # ----------------------------------------------------------------------
 
@@ -123,6 +146,9 @@ rm -rf third-party/
  -DWITH_SvtEnc=ON \
  -DWITH_SvtEnc_PLUGIN=OFF \
 %endif
+%if %{with bootstrap}
+ -DWITH_EXAMPLE_HEIF_VIEW=OFF \
+%endif
  -DWITH_UNCOMPRESSED_CODEC=ON \
  -Wno-dev
 

                 reply	other threads:[~2026-07-30 20:23 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=178544300579.1.548703855333497447.rpms-libheif-e740e76b5b1b@fedoraproject.org \
    --to=awilliam@redhat.com \
    --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