|
From: | Maxim Cournoyer |
Subject: | [bug#51428] core-updates-frozen-batched-changes built and ready to merge |
Date: | Wed, 27 Oct 2021 14:00:07 -0400 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Ludovic Courtès <ludo@gnu.org> writes: > Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis: > >> +(define %gdk-pixbuf-loaders-cache-file >> + "lib/gdk-pixbuf-2.0/2.10.0/loaders.cache") > > A comment indicating that this file is built by the hook would be nice, > but let’s not trigger a rebuild just for that. I've added the following comment: ;; This file is to be generated by the ;; `generate-gdk-pixbuf-loaders-cache' build phase defined below. > Isn’t the hard-coded version number going to cause troubles when > gdk-pixbuf is upgraded? Or if we have some packages using a newer > version while others remain on 2.10.0? I was puzzled by it at the beginning, but it seems some historical related version string that isn't meant to change. Even newer versions of gdk-pixbuf refer to this older version in their documentation/build system. Thank you! Maxim
[Prev in Thread] | Current Thread | [Next in Thread] |