<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Mon, 2010-09-20 at 16:08 +0300, Adrian Bunk wrote: <BLOCKQUOTE TYPE=CITE> <TT>Maintaining a Linux platform that builds its components from git [1] </TT> <TT>that until half a year ago used libtool 1.5 I also ran into the problem </TT> <TT>that more and more components no longer work with libtool 1.5 (including </TT> <TT>several X components). My general impression at that time was that no </TT> <TT>upstream tests its code with libtool 1.5 anymore.</TT> </BLOCKQUOTE> In fact, creating tarballs is not a centralized process. Any developer can create and publish a tarball, not being aware of the libtool version. There is nothing wrong with that, so as long as the modules configuration specify minimum versions. This is done explicitly for Autoconf with AC_INIT but implicitly for automake and libtool by using statements that can only be found at a specific version, or up. <BLOCKQUOTE TYPE=CITE> <TT>Also note that bumping the libtool requirement would affect only people</TT> <TT>building from git, not normal users building from tarballs.</TT> </BLOCKQUOTE> Thanks, that's the kind of info I was looking for. </BODY> </HTML>