On Thursday, March 20, 2014, David Evans <dev...@macports.org> wrote:
> On 3/20/14 3:01 PM, Adam Mercer wrote: > > On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch > > <ebori...@macports.org<javascript:;>> > wrote: > > > >> What was broken that needed fixing (by the original change)? Is there a > >> particular port that needed the change? Is there another way to fix it > >> without modifying automake? > >> > The answer is yes, any port that uses AM_PYTHON_PATH to discover the > Python install > prefix will fail on MacPorts (or any other installation of Python into a > non-standard path) > without intervention and there are quite a few. > > In the past this has been handled typically by applying a similar patch > to the configure file > provided with each project being ported. This works and the patch here > does not interfere > with this because the configure file is not being regenerated. > > However, increasingly, ports need to use autoreconf or even autogen.sh > to regenerate configuration > files prior to build for some other reason (intltool perl issues for > instance). This again effects a > large number of ports. In this case, patching of the configure file is > impractical and the required > patch to configure.ac amounts to replacing AM_PYTHON_PATH with custom > code that is often > package specific. This change to automake makes that unnecessary. > > Have to head home now but will follow up later this evening. In the > meantime, please don't revert > this change on your own as there are many ports that WILL be broken. > If, we, as a group decide > that that is the preferred approach, I will make the change after the > effected ports have been re-written. > > Thanks > > PS What ever happened to the doctrine that if you mix code in other > installation prefixes with MacPorts > ports, all bets are off and results are not guaranteed? > Dave, Any updates on the ports that were fixed / simplified by this patch? I've heard it said, and seen multiple requests for "which ones?" and "where are the tickets?" Can you please shed some light on this? Thanks, Eric
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
