htmlin and html files [was: bogofilter 0.93.4 - new current release]

David Relson relson at osagesoftware.com
Mon Jan 10 01:12:55 CET 2005


On Mon, 10 Jan 2005 02:59:06 +0300
Evgeny Kotsuba wrote:

> Evgeny Kotsuba wrote:

..[snip]...

> (beep on)
> (flame on)
> This is native Unix way, it need xmllint that is part of libxml2, then 
> xmlto that is a " is a bash shell script, which also uses the GNU getopt 
> utility (it requires long option support). Currently the only XSL-T 
> processor that is supported is xsltproc, from Daniel Veillard's libxslt 
> <http://xmlsoft.org/XSLT/> package. The xsltproc support requires a 
> system with properly configured XML Catalogs, such as Red Hat Linux 9."
> libxslt uses XXXX that is path YYYY package that requires a ZZZZ system 
> with with properly configured WWWW, that uses...
> [  full tree of dependencies skipped ]
> fully installated and properly configured unix/linux system with  one 
> thousand an one supports and tools
> (flame off)
> (beep off)
> As opposite, for building bogofilter only two things are really used: C 
> compiler and flex, just because  essential part of bogofilter uses flex.

EK,

For bogolexer, bogoutil, bogotune, and bogoupgrade, the .html files are
identical to the .htmlin files you already have.  bogofilter.html and
bogofilter.htmlin are different because the .htmlin has a reference to
@sysconfdir@/bogofilter.cf which needs to be changed to the proper
directory reference.  On a typical linux system that's /etc/bogofilter.cf

It's not appropriate to distribute the .html file because the directory
depends on how/where bogofilter is installed.

As suggested before, just copying *.htmlin to *.html will give you a
usable set of files (with the one issue described above).

Regards,

David



More information about the bogofilter-dev mailing list