On Wed, Jan 23, 2013 at 2:49 PM, Adam Mercer wrote: > > A beta release, 1.13.1b, for the upcoming 1.13.2 has been released: > > <http://lists.gnu.org/archive/html/automake/2013-01/msg00075.html>
Thank you for the link. > As the release notes says "Its main purpose is to re-introduce some > obsolete m4 macros that had been removed too hastily, bringing woes > and problems for distro packagers..." > > Would it make sense to add an automake-devel port? (Disclaimer: I didn't work with ports that had problems with removed features, so I might not have enough information.) In my opinion it hardly makes any sense to introduce a new automake-devel port for a single week and introduce all kinds of problems with conflicting ports automake/automake-devel. 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. Mojca _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
