Patches item #444879, was opened at 2001-07-26 18:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103

Category: None Group: None Status: Open Resolution: None Priority: 7 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index

Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422.

This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch:

1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py.

2. embeds those strings in the pages generated as the html version of a list's archive.

By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py

You probably want to run this patch as follows:

cd <mailman 2.0.6 untarred and unzipped directory> patch -p1 < <this patch file>

See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput.

Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:39

Message: Logged In: YES user_id=75166

indexing-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4

Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:46

Message: Logged In: YES user_id=75166

indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3

Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32

Message: Logged In: YES user_id=75166

An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers.

Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19

Message: Logged In: YES user_id=75166

An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig.

An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers.

Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19

Message: Logged In: YES user_id=12800

Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific?

I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in

Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14

Message: Logged In: YES user_id=12800

Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake?

Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08

Message: Logged In: YES user_id=75166

indexing-2.0.13-0.2.patch just adds a GPL notice to the patch

Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33

Message: Logged In: YES user_id=75166

indexing-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2

Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:23

Message: Logged In: YES user_id=75166

indexing-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13

Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:11

Message: Logged In: YES user_id=75166

indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12

Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50

Message: Logged In: YES user_id=75166

indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11

Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53

Message: Logged In: YES user_id=75166

indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10

Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43

Message: Logged In: YES user_id=75166

indexing-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9

Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:14

Message: Logged In: YES user_id=75166

indexing-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002.

Corrects problem noted or 5 Mar 2002 by nobody

Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41

Message: Logged In: NO

When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is?

Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53

Message: Logged In: YES user_id=75166

indexing-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001

Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48

Message: Logged In: YES user_id=75166

indexing-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge.

Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07

Message: Logged In: YES user_id=75166

This patch should also apply without problems to MM 2.0.8

Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:03

Message: Logged In: YES user_id=75166

This patch should also apply without problems to MM 2.0.7

You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103