On Jul 10, 2007, at 22:02, source_changes@macosforge.org wrote:
Revision: 26883 http://trac.macosforge.org/projects/macports/changeset/26883 Author: boeyms@macports.org Date: 2007-07-10 20:02:27 -0700 (Tue, 10 Jul 2007)
Log Message: ----------- devel/autoconf: * Add port:m4 to depends_lib (Autoconf README states GNU m4 >= 1.4.7 is required, but Tiger only has 1.4.2); * Correct the name of one of the commands that autoreconf calls so that it will actually work with the MacPorts libtool port.
Doesn't that mean that autoconf should also depend on the libtool port?
Revision: 26883 http://trac.macosforge.org/projects/macports/changeset/ 26883 Author: boeyms@macports.org Date: 2007-07-10 20:02:27 -0700 (Tue, 10 Jul 2007)
Log Message: ----------- devel/autoconf: * Add port:m4 to depends_lib (Autoconf README states GNU m4 >= 1.4.7 is required, but Tiger only has 1.4.2); * Correct the name of one of the commands that autoreconf calls so that it will actually work with the MacPorts libtool port.
Doesn't that mean that autoconf should also depend on the libtool port?
Yeah, that makes sense :P Now I know why I had a line that read: depends_run port:gettext when autoconf has no such dependency, and which I naturally deleted with some puzzlement before the commit. I was working on a few ports at once, realised that autoconf had a runtime dependency on something, but put the wrong portname in. Fixed in r26891. Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
participants (2)
-
Boey Maun Suang
-
Ryan Schmidt