On Jan 3, 2013, at 2:17 PM, Rainer Müller <[email protected]> wrote:
>> Note that the backwards incompatibilities in 1.14 will be less trivial to >> fix, so if you see any warnings about INCLUDES, renaming configure.in to >> configure.ac, or MKDIR_P, you should probably fix those now, so you don't >> get bit by 1.14. > > Should we create a automake-devel port now to test changes early or is > it enough to just fix the warnings reported by automake @1.13 to be safe? I'd say both. Fix the warnings from automake-1.13 and make an automake-devel port that we devs can live on in order to find and fix these issues ahead of time. > We could also keep an automake-1.13 port around (as we did earlier for > both automake and autoconf). We'll see what the fallout is like. If it turns out that many ports are too difficult to fix, we can add an automake113 port, but I'd rather not keep too many of these around. --Jeremy _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
