So... :)
This trickle down effect of needing A, to find it needs B and C, and
that B and C need D and E, and that can go on a while. Look what I
did...
( One small issue with the mysql connector still, and I have a few
questions about how to chain these all together, since there is an
Scott Haneda wrote:
I think this is telling:
- ERROR: Net::DNS::Resolver::Programmable is not installed
- ERROR: Error is not installed
- ERROR: NetAddr::IP is not installed
- ERROR: version is not installed
* Optional prerequisite NetAddr::IP is not installed
I can probably find
Turns out this is not ASSP, or env vars at all. I distilled it down
to a simple test...
#!/opt/local/bin/perl --
use strict;
our $AvailSPF2 = eval(use Mail::SPF; 1);
if ($AvailSPF2) {
print true\n;
my $ver = eval('Mail::SPF-VERSION');
print $ver
} else {
Looking back over the install log:
Warning: violation by /usr
Warning: p5-mail-spf violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended),
it will be an error in future releases!
--- Installing p5-mail-spf @v2.006_0
I did some
Scott Haneda wrote:
Looking back over the install log:
Warning: violation by /usr
Warning: p5-mail-spf violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended), it
will be an error in future releases!
--- Installing p5-mail-spf
On Jan 23, 2009, at 3:43 AM, Joshua Root wrote:
Scott Haneda wrote:
Looking back over the install log:
Warning: violation by /usr
Warning: p5-mail-spf violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is
intended), it
will be an error in
Scott Haneda wrote:
port contents p5-mail-spf | grep -v opt
Port p5-mail-spf contains:
/usr/sbin/spfd
So, how does not resolve this? And I thought ports expressly prevented
this, or is this just the port makers job to prevent it? Since ports
noticed it, I would think it would have
On Sat, Jan 24, 2009 at 08:19:51AM +1100, Joshua Root said:
Scott Haneda wrote:
port contents p5-mail-spf | grep -v opt
Port p5-mail-spf contains:
/usr/sbin/spfd
So, how does not resolve this? And I thought ports expressly prevented
this, or is this just the port makers job to
On Jan 23, 2009, at 1:29 PM, Bryan Blackburn wrote:
The Mail::SPF Build.PL file has:
install_path= {
'sbin' = '/usr/sbin'
},
so it sounds like it needs to be patched to install into the proper
location. The following should do it:
post-extract {
reinplace
Funny, OS X has this damn mod built right in, I tested it, and it
works, forcing the test on ports perl may be telling:
/opt/local/bin/perl -MMail::SPF::Query -le 'print for Mail::SPF::Query-
new( \
helo = shift, ipv4 = shift, sender = shift)-
result' \
Duh, that was a line to test mail:spf:query, which also was not
working, I made a port for sys::hostname:long and now, hooray, I have
all but one port working...
Still stuck on this mail:spf but I am now 99% there on the modules,
and may, one day, before I turn 34, get get to work on ASSP
I think this is telling:
- ERROR: Net::DNS::Resolver::Programmable is not installed
- ERROR: Error is not installed
- ERROR: NetAddr::IP is not installed
- ERROR: version is not installed
* Optional prerequisite NetAddr::IP is not installed
I can probably find the first, but what is Error
I have this solved, but I do not know how to solve this in a way that
works for MacPorts. I am assuming there is a solution for the issues,
since it seems it would be common to many perl ports.
perl uses @INC to figure out where your perl modes are, you can check
with:
perl -e 'print
On Jan 22, 2009, at 14:41, Scott Haneda wrote:
There seems to be two ways to solve this:
1. Add the directory to the PERL5LIB environment variable.
2. Add use lib 'directory'; in your Perl script.
I think the first way is simplest, but not so portable. I am not
even sure a port file can
On Jan 22, 2009, at 4:30 PM, Ryan Schmidt wrote:
On Jan 22, 2009, at 14:41, Scott Haneda wrote:
There seems to be two ways to solve this:
1. Add the directory to the PERL5LIB environment variable.
2. Add use lib 'directory'; in your Perl script.
I think the first way is simplest, but not so
Hello,
In that the variable acts two different ways in two different
locations, I would look to where the variable is set and for where
the setting may change or for a broken link that causes @INC to be
used as a local variable instead of a global.
Frank
On Jan 22, 2009, at 12:41 PM,
Forigve me... Would this var be in the ASSP code, or in the perl mod?
I would be more than happy to track it down, but I do not fully
understand how this @INC variable works.
On Jan 22, 2009, at 7:29 PM, Frank J. R. Hanstick wrote:
Hello,
In that the variable acts two different ways in
ASSP just calls Email::Valid, so I have a feeling it is in the
Email::Valid code itself. I am going to probe the perl beginners list.
On Jan 22, 2009, at 8:51 PM, Frank J. R. Hanstick wrote:
Hello,
Which is a little too deep for me. I am only indicating anomalies
from expected behavior
Hello, this may be getting a little outside the scope of what this
list can help me with. Hopefully we can solve it so I can actually
get my email server where I want.
I downloaded the ASSP package
http://superb-east.dl.sourceforge.net/sourceforge/assp/ASSP_1.4.3.1-Install.zip
The notes
I think I may have found some of the problem, from the email::valid
docs:
If you installed the module into an alternative directory, you will
need to let Perl know where it can be found: use
lib /path/to/my/modules;
use Email::Valid;
I made a test case
use Email::Valid;
print
Hello,
It sounds like opt/local is not the first location the path
environment looks for perl. This is a problem when several versions
of a program exists because unless a prefix is supplied, the default
program will always be found in the order of the pathname (first
detected). If
I am telling ASSP where the new perl is, this issue is that some
modules, only three of 15 or more, are being looked for in the wrong
spot.
I do not know if I should solve this in the port, by editing the
source of the app, or if there is some other way. I actually hope
there is some
Hello,
The problem I had with two gcc's was that one call to the gcc was
done direct (gcc) instead of an indirect prefix variable [ ($SRC)
gcc ]. I would look into ASSP to be sure that all calls to perl
modules use the indirect method. There may be some elements where
the call is direct
I will look into it, thanks. If I can not get more definitive answers
here, I also moved into the perl mail list as well.
The ASSP dev just told me to use CPAN, so I do not think he has any
interest in working this out. I personally feel it is a bug in ASSP,
since other mods work, and
24 matches
Mail list logo
