[Mailman-Users] Re: mailman (2.0.11) + htdig integration - empty result page

[Richard Barrett]

At 11:15 30/05/2002 +0200, Zdenek Pizl wrote:
>Dne st 29. kvìten 2002 18:54 jste napsal(a):
> > At 17:49 29/05/2002 +0200, Zdenek Pizl wrote:
>
> > Just a point of clarification. Are you using the Mailman-htdig integration
> > patches 444879 and 444884 posted on sourceforge?
>
>yes, i am using the patches for 2.0.11 mailman
>
> >
> > Each Mailman list has its own htdig configuration file which is
> > automatically generated by the code added to Mailman when the first message
> > is posted to that list after installation of the patch.
>
>i understand why it is done that way
>
> >
> > [If you want to know why things are organized this way then think about
> > dealing with the issue of security for private archives under search and
> > the need to isolate list search indexes for lists from each other.]
> >
> > The way you have fixed the problem will only apply to the list whose htdig
> > conf file you have edited. I doubt you want to have a career editing these
> > htdig conf files as a new one is created for each new archived mailing list
> > on your system.
> >
> > You really want to get at the root of your problem which is what is wrong
> > with your htdig installation such that htsearch cannot find the default
> > htdig COMMON_DIR. The ./configure and make install for htdig should have
>
>i cannot change htdig instalation. It may be used in many different ways on
>our intranet server ...
>
> > If you are really determined not to fix the htdig side of things then it is
> > possible to change the code that generates the htdig conf files for the
> > lists to try and compensate. If you want I'll point you in the direction of
> > the source code to change but at that point you'll have to be your own
> > support person for the revised code.
>
>it would be nice. i am not familiar with python, but i hope it will be clear
>after your targeting the problem. Does it has something to do with mailman's
>command bin/newlist ??

Zdenek

I'm not convinced you will not encounter problems with his but here goes.

In light of your problem I am adding an extra feature to patch 444884. It 
allows you to specify an arbitrary set of htdig config attributes that are 
to be added at the top of each per mailing list htdig conf file that is 
generated.

You should assign the string that you want inserted at the top of each 
htdig conf file as the value of the Mailman parameter HTDIG_EXTRAS in 
$prefix/Mailman/mm_cfg.py.

You can have the honour of testing this new feature. Below is the content 
of a patch which you should apply to your Mailman build directory which has 
had the 444879 and 444884 patches applied and in the same way as you 
applied those patches.

Let me know if it works OK and helps solve your problem. If it does I'll 
update the main 444884 patch

Richard


Patch file content starts----------------------------------------------------
diff -r -u -P mailman-2.0.11-x/Mailman/Archiver/HyperArch.py 
mailman-2.0.11-y/Mailman/Archiver/HyperArch.py
--- mailman-2.0.11-x/Mailman/Archiver/HyperArch.py      Thu May 30 11:33:33 
2002
+++ mailman-2.0.11-y/Mailman/Archiver/HyperArch.py      Thu May 30 12:20:26 
2002
@@ -603,6 +603,7 @@
  # Taken from the example config file for ht://Dig, with most comments excised
  # See the htdig.conf from the distribution you have installed
  #
+%(htdig_extras)s
  database_dir: %(databases)s
  start_url: %(starturl)s
  limit_urls_to: ${start_url}
@@ -852,6 +853,7 @@
               "indexing_enable": mm_cfg.ARCHIVE_INDEXING_ENABLE,
               "indexing_disable": mm_cfg.ARCHIVE_INDEXING_DISABLE,
               "htdig_url": htdigfiles,
+             "htdig_extras" = mm_cfg.HTDIG_EXTRAS,
              }
          # we need to changes paths to be relative to file system of
          # remote machine if we are not running htdig on mailman machine
diff -r -u -P mailman-2.0.11-x/Mailman/Defaults.py.in 
mailman-2.0.11-y/Mailman/Defaults.py.in
--- mailman-2.0.11-x/Mailman/Defaults.py.in     Thu May 30 11:33:33 2002
+++ mailman-2.0.11-y/Mailman/Defaults.py.in     Thu May 30 12:17:31 2002
@@ -573,6 +573,20 @@
  HTDIG_MAILMAN_LINK = 'htdig-mailman'
  HTDIG_RUNDIG_PATH = '/usr/local/bin/rundig'

+# you can use the HTDIG_EXTRAS parameter to add arbitrary htdig
+# configuration attributes to per list htdig config files. The string
+# value you specify is inserted verbatim at the top of each htdig conf
+# file when it is generated. The default value does nothing. Make sure
+# you understand what you are doing before you fool with this facility.
+HTDIG_EXTRAS = """ \
+# start of extra site specific htdig configuration attributes
+#
+# replace these line with your htdig config attribute declarations
+# as defined at http://www.htdig.org/confindex.html
+#
+# end of extra site specific htdig configuration attributes
+"""
+
  # remote htdig support parameters for mailman-htdig integration
  # provides support for running htdig on a different machine from the one
  # running mailman but one having NFS access to the installation directory
Patch file content ends----------------------------------------------------