On Mon, May 13, 2002 at 03:55:28PM -0500, David T-G wrote:
> Theo, et al --
> % I don't know how it'll find the rules files, but that may be handled
> % as well. To be honest, I haven't actually done a install in non-standard
> % location with SA, so ... :|
>
> That might be a reason to build with PREFIX and LIB set even if I don't
> do an install.
the -c option for spamassassin tells it where to find the rules
directory.
On Mon, May 13, 2002 at 03:54:00PM -0500, David T-G wrote:
> Michael --
>
> ...and then Michael Stenner said...
> % unpack the tarball in ~/local/
>
> I saw that but originally shied away from that; why would I want source
> in there? I think I see that it might be helpful, though...
The distinction between source and executable gets a bit fuzzy when
the program is pure perl :)
> % Then, cd into that directory and do "perl Makefile.PL; make". There's
> % no need to do a "make install".
>
> Ahhhh... And the script, when called by procmail, should happily find
> its module because it will be looking in the same directory. I get it.
Precisely. It knows where it's modules are because it knows where
_it_ is.
> % :0fw
> % | $HOME/lib/SpamAssassin/spamassassin -P -a -c $HOME/lib/SpamAssassin/rules
>
> Thatnks for the handy help; I'll note this.
yeah, if you do it my way, the -c option is necessary.
-Michael
--
Michael Stenner Office Phone: 919-660-2513
Duke University, Dept. of Physics [EMAIL PROTECTED]
Box 90305, Durham N.C. 27708-0305
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
