MacPorts automake and python

[Sean Farley]

Adam Mercer <ram at macports.org> writes:

> On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley <sean at macports.org> wrote:
>
>> I tend to agree with you but need help seeing how this worked
>> before. What path did automake pick up before this change?
>
> If you look at the patch you can see the original paths:
>
> <http://trac.macports.org/browser/trunk/dports/devel/automake/files/patch-m4-python.m4.diff>
>
> The original paths are:
>
> AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
> AC_SUBST([PYTHON_EXEC_PREFIX], ['${exec_prefix}'])
>
> Just to clarify this isn't the MacPorts prefix but the prefix for the
> running configure process.

Right, sorry, I meant more along the lines of:

Before: my project installed into /path/foo/a
After:  my project installed into /path/foo/b