compile time options

[Greg Louis]

On 20030929 (Mon) at 0903:50 -0400, David Relson wrote:
> On Mon, 29 Sep 2003 14:05:16 +0200
> Boris 'pi' Piwinger <3.14 at logic.univie.ac.at> wrote:
> 
> > David Relson wrote:
> > 
> > >> > line 2 FAIL: t.grftest
> > > 
> > > As planned.  WONTFIX.
> > > 
> > > The regression tests, i.e. "make check", _require_ that bogofilter
> > > be built with all three algorithms included.  Having the tests test
> > > different build combinations is not worth the effort.
> > 
> > So what is the way to go?
> > 
> > configure && make && make check && configure
> > --disable-graham-method --disable-robinson-method && make &&
> > make install

What I do is
./configure --prefix=/usr --disable-robinson-method --disable-graham-method
make
src/bogofilter -Mv <../test20
# visually inspect output of this sanity check on 20 each of
# carefully-chosen spam and nonspam; if ok, proceed
checkinstall make install-strip
# see how filtering personal mail performs for a few hours
# if all's well, copy the package to my work mail servers and install

> "make check" is very useful for Matthias and me as our changes often
> result in a broken program.  It's also useful when running a new release
> in an unusual environment, i.e. non-intel or non-Linux, because this
> catches portability issues.  Since you're on intel Linux, there's no
> real need for you to use it.

Agreed.  And anyway, you could always do make -k check and run the
thing anyway if the tests that don't fail are of any interest to you.

-- 
| G r e g  L o u i s         | gpg public key: 0x400B1AA86D9E3E64 |
|  http://www.bgl.nu/~glouis |   (on my website or any keyserver) |
|  http://wecanstopspam.org in signatures helps fight junk email. |