On Tue, 2014-07-15 at 22:34 -0500, Chris wrote:
> On Wed, 2014-07-16 at 04:26 +0200, Karsten Bräckelmann wrote:
> > On Tue, 2014-07-15 at 00:11 -0500, Chris wrote:
> > > dbg: plugin: loading Mail::SpamAssassin::Plugin::DCC
> > > from /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm
> > 
> > Debug states loading a plugin from "an explicitly given absolute
> > referenced file name", rather than resolving from @INC (in which case
> > there literally would be reported "from @INC").
> > 
> > > warn: plugin: failed to parse plugin 
> > > /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm:
> > > Can't locate 
> > > /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin/DCC.pm
> > > in @INC (you may need to install ...) (@INC contains: ...) at ...
> > 
> > Lint states the same. The explicitly given absolute referenced Perl
> > module cannot be parsed. Because it cannot be located.
> > 
> > The module unable to be located being prefixed with a full, absolute
> > path is another hint. Stock SA loadplugin lines are not absolute, but
> > relative.

> You were right (as I knew you would be) I had a path pointing to an old path
> changed to the correct path and it worked fine.

While that might work now (just like it worked before), don't do that.
"That" being giving absolute paths in the config.

Do NOT give the optional path/to/plugin.pm, unless you REALLY DO need
it. In particular, do not add an explicit path, if you want to use the
Perl module provided by your distro.

And to really include *local* plugins, provide a relative path (to the
current site-wide configuration dir, without a leading slash) as
optional second argument to the loadplugin statement. There's hardly
ever any need for a full absolute path. And if there is, there's
something wrong with your environment.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Reply via email to