Re: MacPorts automake and python

2014-03-20 Thread Mojca Miklavec
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: > >

Re: MacPorts automake and python

2014-03-20 Thread Sean Farley
Adam Mercer writes: > 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: > >

Re: MacPorts automake and python

2014-03-20 Thread Brandon Allbery
On Thu, Mar 20, 2014 at 4:27 PM, Daniel J. Luke 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). > > Of course, thin

Re: MacPorts automake and python

2014-03-20 Thread Adam Mercer
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:

Re: MacPorts automake and python

2014-03-20 Thread Daniel J. Luke
On Mar 20, 2014, at 3:50 PM, Adam Mercer wrote: > On Thu, Mar 20, 2014 at 2:28 PM, Jeremy Lavergne > 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 M

Re: MacPorts automake and python

2014-03-20 Thread Sean Farley
Adam Mercer 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 the MacPort

Re: MacPorts automake and python

2014-03-20 Thread Adam Mercer
On Thu, Mar 20, 2014 at 2:28 PM, Jeremy Lavergne 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 to lead to people forcing

Re: MacPorts automake and python

2014-03-20 Thread Jeremy Lavergne
Isn’t this a pythonism, things install to python’s site-packages directory? On Mar 20, 2014, at 15:25, Adam Mercer 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 into MacPorts p

MacPorts automake and python

2014-03-20 Thread Adam Mercer
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 w