Re: How to activate an older version of a port

2013-01-17 Thread Jamie Griffin
* Brandon Allbery allber...@gmail.com [2013-01-16 12:32:09 -0500]: On Wed, Jan 16, 2013 at 3:21 AM, Jamie Paul Griffin ja...@kode5.net wrote: I installed mutt devel myself into /usr/local, rather than using Macports, I don't recall the reasons why; I haven't experienced any problems so

Re: How to activate an older version of a port

2013-01-17 Thread Ryan Schmidt
On Jan 17, 2013, at 02:07, Jamie Griffin ja...@kode5.net wrote: * Brandon Allbery allber...@gmail.com [2013-01-16 12:32:09 -0500]: On Wed, Jan 16, 2013 at 3:21 AM, Jamie Paul Griffin ja...@kode5.net wrote: I installed mutt devel myself into /usr/local, rather than using Macports, I don't

Re: How to activate an older version of a port

2013-01-16 Thread Jamie Paul Griffin
* Jerry lancebo...@qwest.net [2013-01-15 00:29:31 -0700]: On Jan 15, 2013, at 12:13 AM, Ryan Schmidt wrote: On Jan 14, 2013, at 18:24, Jerry wrote: On Jan 13, 2013, at 4:43 PM, Ryan Schmidt wrote: On Jan 12, 2013, at 00:39, Jerry wrote: Since /opt/local is seen before

Re: How to activate an older version of a port

2013-01-16 Thread Brandon Allbery
On Wed, Jan 16, 2013 at 3:21 AM, Jamie Paul Griffin ja...@kode5.net wrote: I installed mutt devel myself into /usr/local, rather than using Macports, I don't recall the reasons why; I haven't experienced any problems so far but is it likely, then, that I will? I don't think very much

Re: How to activate an older version of a port

2013-01-14 Thread Jerry
On Jan 13, 2013, at 4:43 PM, Ryan Schmidt wrote: On Jan 12, 2013, at 00:39, Jerry wrote: Since /opt/local is seen before /usr/local/ (which has automake 1.9 in it), I want to temporarily roll back macports automake to 1.11.3. I get this: Note that having software installed in /usr/local

Re: How to activate an older version of a port

2013-01-14 Thread Ryan Schmidt
On Jan 14, 2013, at 18:24, Jerry wrote: On Jan 13, 2013, at 4:43 PM, Ryan Schmidt wrote: On Jan 12, 2013, at 00:39, Jerry wrote: Since /opt/local is seen before /usr/local/ (which has automake 1.9 in it), I want to temporarily roll back macports automake to 1.11.3. I get this: Note

Re: How to activate an older version of a port

2013-01-14 Thread Jerry
On Jan 15, 2013, at 12:13 AM, Ryan Schmidt wrote: On Jan 14, 2013, at 18:24, Jerry wrote: On Jan 13, 2013, at 4:43 PM, Ryan Schmidt wrote: On Jan 12, 2013, at 00:39, Jerry wrote: Since /opt/local is seen before /usr/local/ (which has automake 1.9 in it), I want to temporarily roll

Re: How to activate an older version of a port

2013-01-13 Thread Ryan Schmidt
On Jan 12, 2013, at 00:39, Jerry wrote: Since /opt/local is seen before /usr/local/ (which has automake 1.9 in it), I want to temporarily roll back macports automake to 1.11.3. I get this: Note that having software installed in /usr/local is likely to cause you problems with MacPorts, which

Re: How to activate an older version of a port

2013-01-12 Thread Jerry
On Jan 11, 2013, at 11:49 PM, Lawrence Velázquez wrote: On Jan 12, 2013, at 1:39 AM, Jerry lancebo...@qwest.net wrote: I want to temporarily roll back macports automake to 1.11.3. I get this: $ port installed automake The following ports are currently installed: automake @1.11.3_0

How to activate an older version of a port

2013-01-11 Thread Jerry
Hi list, I'm trying to do a git bisection on LyX to find a problem. This is _not_ a macports build but done straight from the LyX repository. Newer versions build OK but on some somewhat older sources, I'm getting a complaint that only versions of automake 1.8 through 1.11 are supported, and I

Re: How to activate an older version of a port

2013-01-11 Thread Lawrence Velázquez
On Jan 12, 2013, at 1:39 AM, Jerry lancebo...@qwest.net wrote: I want to temporarily roll back macports automake to 1.11.3. I get this: $ port installed automake The following ports are currently installed: automake @1.11.3_0 automake @1.11.4_0 automake @1.12_0 automake @1.12.2_0