Hi
Since automake was bumped to 1.14.1_1 it can't be used to build any
python software outside of MacPorts as it always tries to install the
python modules into MacPorts prefix. I understand why we want to
ensure that ports always installs modules into the MacPorts prefix,
but I can't understand
Isn’t this a pythonism, things install to python’s site-packages directory?
On Mar 20, 2014, at 15:25, Adam Mercer r...@macports.org wrote:
Since automake was bumped to 1.14.1_1 it can't be used to build any
python software outside of MacPorts as it always tries to install the
python modules
On Thu, Mar 20, 2014 at 2:28 PM, Jeremy Lavergne
jer...@lavergne.gotdns.org wrote:
Isn't this a pythonism, things install to python's site-packages directory?
The main point is that we don't want random things, outside the
control of MacPorts, installed in the MacPorts prefix. This is just
going
Adam Mercer r...@macports.org writes:
Hi
Since automake was bumped to 1.14.1_1 it can't be used to build any
python software outside of MacPorts as it always tries to install the
python modules into MacPorts prefix. I understand why we want to
ensure that ports always installs modules into
On Mar 20, 2014, at 3:50 PM, Adam Mercer r...@macports.org wrote:
On Thu, Mar 20, 2014 at 2:28 PM, Jeremy Lavergne
jer...@lavergne.gotdns.org wrote:
Isn't this a pythonism, things install to python's site-packages directory?
The main point is that we don't want random things, outside the
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley s...@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:
On Thu, Mar 20, 2014 at 4:27 PM, Daniel J. Luke dl...@geeklair.net wrote:
for perl, there's a 'vendor' directory (where we install stuff) and a
'site' directory (where anything goes). If an end-user installs his/her own
perl modules, they end up in the site directory (which is in $prefix).
Adam Mercer r...@macports.org writes:
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley s...@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:
On Thu, Mar 20, 2014 at 9:47 PM, Adam Mercer wrote:
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley 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:
