MM> The usual procedure is:
MM> perl Makefile.PL; make; make test; make install
Ah, that now works only once! Now only
set -e; perl Makefile.PL; make clean; perl Makefile.PL; make; make install
will work each time, even if a few months pass between one's upgrades.
Hmmm, they might want to docum
Maybe they changed something. In the past
perl Makefile.PL PREFIX=$HOME/.spamassassin-tree
also took care of where bin/spamassassin went. Now it seems left behind,
due to this suspicious commented out code?
# needs to be added to MY::install if used
#bin__install: $(INST_SCRIPT)/sa-filter
#
$ sa-update --install http://daryl.dostech.ca/sa-update/asf/>
> $ spamassassin
> spamassassin: spamassassin script is v3.003000, but using modules v3.004000
ostech.ca/sa-update/asf/> $ spamassassin
> spamassassin: spamassassin script is v3.003000, but using modules v3.004000
It should be alright to use the SVN trunk version, I'm using it here.
> spamassassin: spamassassin script is v3.003000, but using modules v3.004000
Apparently y
Help, I dared to update from SVN, and now spamassassin refuses to run:
$ svn update
$ make install
$ sa-update --install http://daryl.dostech.ca/sa-update/asf/>
$ spamassassin
spamassassin: spamassassin script is v3.003000, but using modules v3.004000
