Re: Perl error, once and for all

On 2009-03-03 11:49:12 -0800, Bradley Giesbrecht wrote: > Maybe we could add a port "macports-profile" that would be a script > similar to: > /opt/local/share/macports/setupenv.bash Yes, this is a rather standard way of doing such things. > I suppose the file /opt/local/etc/maports_profile.conf

Re: Perl error, once and for all

On Mar 3, 2009, at 7:55 AM, Vincent Lefevre wrote: On 2009-03-03 07:30:18 -0800, Bradley Giesbrecht wrote: On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: if [ -n "$PERL5LIB" ]; then PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" else export PERL5LIB PERL5LIB="/opt/local/lib/perl5

Re: Perl error, once and for all

On 2009-03-03 07:30:18 -0800, Bradley Giesbrecht wrote: > On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: >>> if [ -n "$PERL5LIB" ]; then >>> PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" >>> else >>> export PERL5LIB >>> PERL5LIB="/opt/local/lib/perl5/vendor_perl" >>> fi > > My path

Re: Perl error, once and for all

On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: On 2009-03-02 01:18:41 +0100, Vincent Lefevre wrote: Yes, but MacPorts should not override the user's settings (i.e. it should test whether PERL5LIB is already set...). One should end up with something like: if [ -n "$PERL5LIB" ]; then PERL5

Re: Perl error, once and for all

On 2009-03-02 01:18:41 +0100, Vincent Lefevre wrote: > Yes, but MacPorts should not override the user's settings (i.e. it > should test whether PERL5LIB is already set...). One should end up > with something like: > > if [ -n "$PERL5LIB" ]; then > PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendo

Re: Perl error, once and for all

On 2009-02-28 21:35:59 -0800, Bradley Giesbrecht wrote: > I just want to install something that needs a perl and a p5 module. Do I > really need to RTFM for that? MacPorts can do things for you or tell you what to do. Otherwise, yes, you should RTFM. But this is not specific to perl... > If I wa

Re: Perl error, once and for all

On 2009-03-01 01:00:43 -0800, Scott Haneda wrote: > So, let me get this straight, if MacPorts was to install a .profile with > a certain PERL5LIB env var in it, this issue is solved? Yes, but MacPorts should not override the user's settings (i.e. it should test whether PERL5LIB is already set...)

Re: Perl error, once and for all

On Mar 1, 2009, at 1:43 AM, Joshua Root wrote: Scott Haneda wrote: I have seen many posts, where a port is not installing. The reply from other users has been "you need to -f it, some ports are just that way", and that is not the right info, it will spiral out of control, to the point where

Re: Perl error, once and for all

Scott Haneda wrote: > I have seen many posts, where a > port is not installing. The reply from other users has been "you need > to -f it, some ports are just that way", and that is not the right info, > it will spiral out of control, to the point where as illustrated above, > they blindly -f thing

Re: Perl error, once and for all

On Feb 28, 2009, at 9:35 PM, Bradley Giesbrecht wrote: On Feb 28, 2009, at 6:53 PM, Vincent Lefevre wrote: On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: I think you have to modify the module to "use lib" and supply a path. No need to do that. Just modify PERL5LIB in your environment once

Re: Perl error, once and for all

On Feb 28, 2009, at 6:53 PM, Vincent Lefevre wrote: On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: I think you have to modify the module to "use lib" and supply a path. No need to do that. Just modify PERL5LIB in your environment once and for all (you or MacPorts had to do the same for $PAT

Re: Perl error, once and for all

Quoting some freebsd'ers: http://forums.freebsd.org/showthread.php?t=2031 I have freeBSD 7.0 installed. I've updated my perl installation from perl5-8-8 tu perl5.8.9 is it possible to upgrade all installed perl modules from ports using a one single command ? Well, there is a command called pe

Re: Perl error, once and for all

On Feb 28, 2009, at 6:59 PM, Vincent Lefevre wrote: On 2009-02-26 10:16:23 -0500, Daniel J. Luke wrote: On Feb 26, 2009, at 7:28 AM, Scott Haneda wrote: Does anyone know how CPAN solves this? CPAN installs overwrite the perl-provided module with the newer one (this is the whole reason why w

Re: Perl error, once and for all

On Feb 28, 2009, at 6:53 PM, Vincent Lefevre wrote: On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: I think you have to modify the module to "use lib" and supply a path. No need to do that. Just modify PERL5LIB in your environment once and for all (you or MacPorts had to do the same for $P

Re: Perl error, once and for all

On 2009-02-26 10:16:23 -0500, Daniel J. Luke wrote: > On Feb 26, 2009, at 7:28 AM, Scott Haneda wrote: >> Does anyone know how CPAN solves this? > > CPAN installs overwrite the perl-provided module with the newer one > (this is the whole reason why we have a problem). Well, that's a MacPorts spe

Re: Perl error, once and for all

On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: > I think you have to modify the module to "use lib" and supply a path. No need to do that. Just modify PERL5LIB in your environment once and for all (you or MacPorts had to do the same for $PATH, $LIBRARY_PATH, $C_INCLUDE_PATH or whatever, anyw

Re: Perl error, once and for all

On 2009-02-26 05:51:33 +, Eric Hall wrote: > For some (if not all) of the p5-* ports that have recently > sprouted problems, its the man pages that are the issue, not the > modules themselves. I haven't had a chance to look into what > can be done to avoid the man page collisions. The m

Re: Perl error, once and for all

On Feb 26, 2009, at 7:28 AM, Scott Haneda wrote: Does anyone know how CPAN solves this? CPAN installs overwrite the perl-provided module with the newer one (this is the whole reason why we have a problem). -- Daniel J. Luke ++ | *

Re: Perl error, once and for all

On Feb 26, 2009, at 12:26 AM, Ryan Schmidt wrote: On Feb 26, 2009, at 02:20, Scott Haneda wrote: MacPorts operates under the assumption that exactly one port will provide a file at a given path. The combination of perl5.8 and whatever module it is that you were installing that wanted to ins

Re: Perl error, once and for all

On Feb 26, 2009, at 02:20, Scott Haneda wrote: MacPorts operates under the assumption that exactly one port will provide a file at a given path. The combination of perl5.8 and whatever module it is that you were installing that wanted to install Test/Builder/Module.pm is in violation of th

Re: Perl error, once and for all

On Feb 25, 2009, at 11:53 PM, Ryan Schmidt wrote: Is this saying, the new port I am installing, has in it "Module.pm", and is trying to write over /opt/local/lib/perl5/5.8.9/ Test/Builder/Module.pm ? If that is the case, would it not be acceptable to version check the to be installed, agains

Re: Perl error, once and for all

On Feb 26, 2009, at 01:44, Scott Haneda wrote: On Feb 25, 2009, at 9:51 PM, Eric Hall wrote: That feels dirty to me, why not just -f all p5 installs then? If that is the real solution, why not have ports look for p5 and auto add the - f? I am sure this is a bad idea, but if this is the n

Re: Perl error, once and for all

On Feb 25, 2009, at 9:51 PM, Eric Hall wrote: That feels dirty to me, why not just -f all p5 installs then? If that is the real solution, why not have ports look for p5 and auto add the - f? I am sure this is a bad idea, but if this is the norm, users are more or less going to do this anywa

Re: Perl error, once and for all

On Wed, Feb 25, 2009 at 01:21:38PM -0800, Scott Haneda wrote: > On Feb 25, 2009, at 7:03 AM, Daniel J. Luke wrote: > >On Feb 25, 2009, at 12:49 AM, Scott Haneda wrote: > >>Sorry, I know this has been explained before, > > > >yes, very recently. > > Can you point me to they "why", not just the solu

Re: Perl error, once and for all

On 2009-02-25 13:21:38 -0800, Scott Haneda wrote: > That feels dirty to me, why not just -f all p5 installs then? No! Any port that needs -f is broken. Note: -f is dangerous. It can trash your system. And it is not compatible with activate/deactivate. -- Vincent Lefèvre - Web:

Re: Perl error, once and for all

On Feb 25, 2009, at 8:39 AM, Daniel J. Luke wrote: How do you know which to choose? I agree that the port should output a message letting you know what to do (for now, and longer term, we need to make it so you don't need to force activate these kinds of perl modules). I want to add som

Re: Perl error, once and for all

On Feb 25, 2009, at 7:03 AM, Daniel J. Luke wrote: On Feb 25, 2009, at 12:49 AM, Scott Haneda wrote: Sorry, I know this has been explained before, yes, very recently. Can you point me to they "why", not just the solution, I want to understand what is the problem? bur I can not find the

Re: Perl error, once and for all

On Feb 25, 2009, at 10:21 AM, Mark Hattam wrote: DEBUG: Executing org.macports.activate (p5-mime-base64) ---> Activating p5-mime-base64 @3.07_0 Error: Target org.macports.activate returned: Image error: /opt/ local/share/man/man3/MIME::Base64.3pm.gz is being used by the active perl5.8 port.

Re: Perl error, once and for all

On 25 Feb 2009, at 15:03, Daniel J. Luke wrote: On Feb 25, 2009, at 12:49 AM, Scott Haneda wrote: Sorry, I know this has been explained before, yes, very recently. bur I can not find the answer: DEBUG: Executing org.macports.activate (p5-mime-base64) ---> Activating p5-mime-base64 @3.07_

Re: Perl error, once and for all

On Feb 25, 2009, at 12:49 AM, Scott Haneda wrote: Sorry, I know this has been explained before, yes, very recently. bur I can not find the answer: DEBUG: Executing org.macports.activate (p5-mime-base64) ---> Activating p5-mime-base64 @3.07_0 Error: Target org.macports.activate returned: Ima

Perl error, once and for all

Sorry, I know this has been explained before, bur I can not find the answer: DEBUG: Executing org.macports.activate (p5-mime-base64) ---> Activating p5-mime-base64 @3.07_0 Error: Target org.macports.activate returned: Image error: /opt/local/ share/man/man3/MIME::Base64.3pm.gz is being used b