On Mon, 19 Oct 2015 21:25:26 +0200
"Yury V. Zaytsev" wrote:
> If you can come up a one-liner patch to make it compatible with old
> glib, we can think of applying it; I have nothing against supporting
> older glib per se, unless it comes with too much of a maintenance
> cost... but I'm not really sure if it's worth it.
Glib version check patch attached.
> Back when I was taking care of backporting mc to older RHELs, I simply
> used to build newer glib statically from within the package and link
> mc to it... that's the route I'd suggest you to go if you care about
> backporting mc to Squeeze.
I'm not interested in backporting MC to Debian Squeeze. I'm building MC
packages for Debian/Ubuntu actual releases (see
https://www.midnight-commander.org/wiki/Binaries) and Squeeze in this
list due to Debian Squeeze LTS.
If support "cost" for Debian Squeeze is going higher (higher than cost
of electricity which buildbot spend to build package) then I will drop
support for Debian Squeeze.
--
WBR, Andrey Tataranovich
diff --git a/m4.include/ac-glib.m4 b/m4.include/ac-glib.m4
index c7fd084..ff892c7 100644
--- a/m4.include/ac-glib.m4
+++ b/m4.include/ac-glib.m4
@@ -78,9 +78,9 @@ AC_DEFUN([AC_CHECK_GLIB], [
AS_HELP_STRING([--with-glib-static], [Link glib statically @<:@no@:>@]))
glib_found=no
-PKG_CHECK_MODULES(GLIB, [glib-2.0 >= 2.14], [glib_found=yes], [:])
+PKG_CHECK_MODULES(GLIB, [glib-2.0 >= 2.26], [glib_found=yes], [:])
if test x"$glib_found" = xno; then
-AC_MSG_ERROR([glib-2.0 not found or version too old (must be >= 2.14)])
+AC_MSG_ERROR([glib-2.0 not found or version too old (must be >= 2.26)])
fi
])
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel