On Wed, Jan 23, 2013 at 8:55 AM, Ryan Schmidt <[email protected]> wrote:
> I agree. Besides, the ports that use automake depend on port:automake so they > cannot benefit from an automake-devel port, unless we change them all to > depend on path:bin/automake:automake. We'd also need to make the same change > in MacPorts base (in ./src/port1.0/portconfigure.tcl) and release a new > version of MacPorts base. Good point, that'd probably be more work than fixing the macros in the first place. >> If 1.13.1 >> already broke so much, it might be easiest to simply switch to 1.13.1b >> in the main automake port now (it probably cannot break more than the >> last version did?) to be able to discover other remaining problems >> before the release of 1.13.2. Then MacPorts can switch to 1.13.2 as >> soon as that version comes out. > > I'd be ok with that. I'd also be ok with just waiting until 1.13.2 is > released. I've updated to 1.13.1b locally to test it out and will keep an eye out for the 1.13.2 release, I don't like the idea of using a beta release for such an important port. Cheers Adam _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
