> On Jul 17, 2015, at 11:32 PM, [email protected] wrote: > > Revision > 138756 > Author > [email protected] > Date > 2015-07-17 21:32:47 -0700 (Fri, 17 Jul 2015) > Log Message > > cutter: use perl5.22; see #48365 > Modified Paths > > • trunk/dports/devel/cutter/Portfile > Diff > > Modified: trunk/dports/devel/cutter/Portfile (138755 => 138756) > > --- trunk/dports/devel/cutter/Portfile 2015-07-18 04:31:22 UTC (rev > 138755) > +++ trunk/dports/devel/cutter/Portfile 2015-07-18 04:32:47 UTC (rev > 138756) > @@ -24,7 +24,7 @@ > > depends_build port:intltool \ > port:pkgconfig \ > - port:p5.16-xml-parser > + port:p5.22-xml-parser
This change looks incomplete. How does the port know to use the files installed by p5.22-xml-parser instead of those installed by p5.16-xml-parser? In this case, I guess the xml-parser dependency is only there because of intltool. The way we want to solve this problem instead is to remove the xml-parser dependency, and use the program's autogen.sh script prior to running the configure script. This will update the intltool configuration process to no longer check for xml-parser. The way I usually do this is to add port:autoconf, port:automake and port:libtool to depends_build, set "use_autoreconf yes", set "autoreconf.cmd ./autogen.sh" (assuming that's the name of the autotools regeneration script provided in the package, which in the case of cutter it is), and set "autoreconf.args" to clear them. Cutter's autogen.sh contains Homebrew-specific code so it will need to be patched to work with MacPorts. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
