On Tue, 2006-06-13 at 16:17 +1200, Michael J. Knox wrote: > Ralf Corsepius wrote: > > On Tue, 2006-06-13 at 15:10 +1200, Michael J. Knox wrote: > > > >>Bill Nottingham wrote: > >> > >>># repoquery --whatrequires --alldeps autoconf213 automake14 automake15 --archlist i686,i386,noarch,src --repoid development --repoid development-source > >>>metacity-0:2.15.5-5.src > >> > >>Fixed. Replaced BR on automake14 with automake, also added gettext to BR > >>to building min mock enviro. > > [snip] > > > Metacity uses automake-1.7, uses AM_MAINTAINER_MODE, the only patch > > affecting the autotools is a one liner, so providing a patch would be > > trivial and painless. > > Hang about.. you said automake 1.7 are you sure? With the sources from your src.rpm: # tar xzf metacity-2.15.5-jun6-2006.tar.gz .. # head -1 metacity-2.15.5-jun6-2006/Makefile.in # Makefile.in generated by automake 1.7.9 from Makefile.am. > It was depending on 1.4 > previously. > > Also, whats the downside of just using 1.9 ? (wanting to understand the > issue :) ) Many subtile behavioral changes potentially affecting a package. Checking whether a package is affected by them is not an easy task. However, in most cases, using automake-1.9 on packages having been designed for 1.7 is harmless. Using automake > 1.4 on packages having been written for 1.4 almost never works. Ralf
