Reverted and revbumped: r118111.
On Mar 22, 2014, at 20:28, Eric A. Borisch wrote:
> On Thursday, March 20, 2014, David Evans wrote:
> On 3/20/14 3:01 PM, Adam Mercer wrote:
> > On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch
> > wrote:
> >
> >> What was broken that needed fixing (by the ori
On Thursday, March 20, 2014, David Evans wrote:
> On 3/20/14 3:01 PM, Adam Mercer wrote:
> > On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch
> > >
> wrote:
> >
> >> What was broken that needed fixing (by the original change)? Is there a
> >> particular port that needed the change? Is there anot
Adam Mercer writes:
> On Thu, Mar 20, 2014 at 9:54 PM, Adam Mercer wrote:
>
>> At the moment we have an automake that doesn't work, that is a major
>> issue and needs to be fixed ASAP. Which ports are broken without this
>> change? Are there tickets?
>
> You still haven't quoted tickets for thi
On Thu, Mar 20, 2014 at 9:54 PM, Adam Mercer wrote:
> At the moment we have an automake that doesn't work, that is a major
> issue and needs to be fixed ASAP. Which ports are broken without this
> change? Are there tickets?
You still haven't quoted tickets for this issue, are there any? This
is
On Thu, Mar 20, 2014 at 6:41 PM, David Evans wrote:
> If you were using a Python that was installed using the
> traditional installation path then
> this would return ${prefix} as the original did.
>
> For instance using python24 returns /opt/local (which is ${prefix) by
> our standard and other
David Evans writes:
> On 3/20/14 3:01 PM, Adam Mercer wrote:
>> On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch
>> wrote:
>>
>>> I think the issue here is that automake is getting patched to *only* support
>>> MacPorts-managed builds, but really automake should still be available for
>>> use
On 3/20/14 3:01 PM, Adam Mercer wrote:
> On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch
> wrote:
>
>> I think the issue here is that automake is getting patched to *only* support
>> MacPorts-managed builds, but really automake should still be available for
>> use to build non-MP software.
> Agr
David Evans writes:
> On 3/20/14 2:57 PM, Adam Mercer wrote:
>> On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
>>
>>> Before: my project installed into /path/foo/a
>>> After: my project installed into /path/foo/b
>> Got you, if I configured using: ./configure --prefix=$HOME/opt
>>
>> the
On Thu, Mar 20, 2014 at 5:57 PM, David Evans wrote:
> What's your motivation for installing it elsewhere? Trying to
> understand but I guess I'm being dense.
Simply because I'm installing manually from source, it isn't part of
MacPorts and shouldn't be installed in the MacPorts prefix.
I work
On 3/20/14 2:57 PM, Adam Mercer wrote:
> On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
>
>> Before: my project installed into /path/foo/a
>> After: my project installed into /path/foo/b
> Got you, if I configured using: ./configure --prefix=$HOME/opt
>
> the the Python modules would be inst
Eric A. Borisch writes:
> On Thursday, March 20, 2014, Sean Farley
> >
> wrote:
>
>>
>> Adam Mercer writes:
>>
>> > On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
>> >
>> >> Before: my project installed into /path/foo/a
>> >> After: my project installed into /path/foo/b
>> >
>> > Got you
On Thursday, March 20, 2014, Sean Farley
>
wrote:
>
> Adam Mercer writes:
>
> > On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
> >
> >> Before: my project installed into /path/foo/a
> >> After: my project installed into /path/foo/b
> >
> > Got you, if I configured using: ./configure --pref
Adam Mercer writes:
> On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
>
>> Before: my project installed into /path/foo/a
>> After: my project installed into /path/foo/b
>
> Got you, if I configured using: ./configure --prefix=$HOME/opt
>
> the the Python modules would be installed in:
> $H
On Thu, Mar 20, 2014 at 4:51 PM, Eric A. Borisch wrote:
> I think the issue here is that automake is getting patched to *only* support
> MacPorts-managed builds, but really automake should still be available for
> use to build non-MP software.
Agreed, that's one of the main concerns I have with
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
> Before: my project installed into /path/foo/a
> After: my project installed into /path/foo/b
Got you, if I configured using: ./configure --prefix=$HOME/opt
the the Python modules would be installed in:
$HOME/opt/lib/python2.7/site-packages
Brining back to dev list; seems like the right place.
On Thu, Mar 20, 2014 at 4:01 PM, Sean Farley wrote:
>
> 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
16 matches
Mail list logo
