[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

building packages only for ports



In GNOME 49, gdk-pixbuf uses glycin (a next generation image loader
written in Rust) by default instead of loading images itself or with
plugins. gdk-pixbuf is used for all GTK apps so this change is
far-reaching. Debian's gdk-pixbuf hasn't switched to glycin yet except
in Experimental.

The webp-pixbuf-loader .deb package would no longer be useful for
architectures that have switched to gdk-pixbuf+glycin. However, there
are several Debian ports that don't have a build of glycin yet.

Is it possible and practical for a Debian source package like
webp-pixbuf-loader to build binary packages only for Debian ports? I
assume the package wouldn't be able to migrate to Testing since ports
don't use Testing.

Another example is jpeg-xl which has a binary package,
libjxl-gdk-pixbuf, but builds several other binary packages.

Is this situation documented anywhere?

Thank you,
Jeremy Bícha


Reply to: