Re: How to activate an older version of a port
* 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 far but is it likely, then, that I will? I don't think very much requires mutt as a build dependency, so you will *probably* be ok. unless you also installed some of its build dependencies there, in which case you may already have a tangled mess that will break if the MacPorts versions of those dependencies are updated incompatibly and some MacPorts install requires them. Hi Brandon, the only library I installed for it was tokyocabinet - so just one. Luckily, since I installed mutt I haven't installed or updated any Macports so I should be able to clear it out and perhaps reinstall with Macports. I believe Maports' version of mutt has tokyocabinet variant with it, which is all I need. I'm glad I saw this thread and asked, even though it's documented I didn't think it would cause so much of a problem. So thanks for confirming that for me. Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 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 requires mutt as a build dependency, so you will *probably* be ok. unless you also installed some of its build dependencies there, in which case you may already have a tangled mess that will break if the MacPorts versions of those dependencies are updated incompatibly and some MacPorts install requires them. Hi Brandon, the only library I installed for it was tokyocabinet - so just one. Luckily, since I installed mutt I haven't installed or updated any Macports so I should be able to clear it out and perhaps reinstall with Macports. I believe Maports' version of mutt has tokyocabinet variant with it, which is all I need. I'm glad I saw this thread and asked, even though it's documented I didn't think it would cause so much of a problem. So thanks for confirming that for me. Yes, mutt-devel has a +tokyocabinet variant. But if you have tokyocabinet installed in /usr/local and you install mutt-devel +tokyocabinet, it might inadvertently use the tokyocabinet in /usr/local instead of the MacPorts one that we want it to use. So be sure to remove /usr/local before you continue with upgrading or installing more ports. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
* 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 /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 is why we do not support having software installed there. https://trac.macports.org/wiki/FAQ#usrlocal I've read this discussion before. I thought it was OK to have stuff in subdirectories of /usr/local but not OK to have stuff /usr/local directly. Is that not correct? I know this is a flamey topic so I won't say more. Yes, having software installed into a prefix below /usr/local is fine. For example, the official MySQL binaries are (used to be?) distributed with a prefix like /usr/local/mysql-X.Y.Z; this is fine. But installing into prefix /usr/local (i.e. files installed into /usr/local/bin, /usr/local/include, /usr/local/lib) can cause problems. Ah--thanks for the clarification. I think I'll be taking a look at this in due course to see if I can clean things up on my machine. Jerry 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? Jamie -- Primary Key: 4096R/1D31DC38 2011-12-03 Key Fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 requires mutt as a build dependency, so you will *probably* be ok. unless you also installed some of its build dependencies there, in which case you may already have a tangled mess that will break if the MacPorts versions of those dependencies are updated incompatibly and some MacPorts install requires them. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 is likely to cause you problems with MacPorts, which is why we do not support having software installed there. https://trac.macports.org/wiki/FAQ#usrlocal I've read this discussion before. I thought it was OK to have stuff in subdirectories of /usr/local but not OK to have stuff /usr/local directly. Is that not correct? I know this is a flamey topic so I won't say more. Jerry How can I activate an older version of automake and then re-activate the newest version later? https://trac.macports.org/wiki/howto/InstallingOlderPort ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 that having software installed in /usr/local is likely to cause you problems with MacPorts, which is why we do not support having software installed there. https://trac.macports.org/wiki/FAQ#usrlocal I've read this discussion before. I thought it was OK to have stuff in subdirectories of /usr/local but not OK to have stuff /usr/local directly. Is that not correct? I know this is a flamey topic so I won't say more. Yes, having software installed into a prefix below /usr/local is fine. For example, the official MySQL binaries are (used to be?) distributed with a prefix like /usr/local/mysql-X.Y.Z; this is fine. But installing into prefix /usr/local (i.e. files installed into /usr/local/bin, /usr/local/include, /usr/local/lib) can cause problems. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 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 is why we do not support having software installed there. https://trac.macports.org/wiki/FAQ#usrlocal I've read this discussion before. I thought it was OK to have stuff in subdirectories of /usr/local but not OK to have stuff /usr/local directly. Is that not correct? I know this is a flamey topic so I won't say more. Yes, having software installed into a prefix below /usr/local is fine. For example, the official MySQL binaries are (used to be?) distributed with a prefix like /usr/local/mysql-X.Y.Z; this is fine. But installing into prefix /usr/local (i.e. files installed into /usr/local/bin, /usr/local/include, /usr/local/lib) can cause problems. Ah--thanks for the clarification. I think I'll be taking a look at this in due course to see if I can clean things up on my machine. Jerry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 is why we do not support having software installed there. https://trac.macports.org/wiki/FAQ#usrlocal How can I activate an older version of automake and then re-activate the newest version later? https://trac.macports.org/wiki/howto/InstallingOlderPort ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 automake @1.11.4_0 automake @1.12_0 automake @1.12.2_0 automake @1.12.5_0 (active) so it should be possible (right?) but I can't find the command to do this although I think I once saw it. How can I activate an older version of automake and then re-activate the newest version later? $ sudo port activate automake @1.11.3_0 $ [yada yada yada] $ sudo port activate automake @1.12.5_0 vq Ah--thanks, Lawrence. Jerry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
How to activate an older version of a port
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 think this is causing the build to fail. 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: $ 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 automake @1.12.5_0 (active) so it should be possible (right?) but I can't find the command to do this although I think I once saw it. How can I activate an older version of automake and then re-activate the newest version later? Thanks, Jerry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to activate an older version of a port
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 automake @1.12.5_0 (active) so it should be possible (right?) but I can't find the command to do this although I think I once saw it. How can I activate an older version of automake and then re-activate the newest version later? $ sudo port activate automake @1.11.3_0 $ [yada yada yada] $ sudo port activate automake @1.12.5_0 vq ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
