On September 19, 2003 at 17:36, Cheryl Trooskin wrote:
* I wish the procmail maintainers would fix version 3.22 and
piping-out-of-memory problem. I guess I need to consider if applying
some of the work-arounds should be put into mharc, as you have done
with yout mk-procmailrc patch.
I'm not holding my breath for procmail 3.23; I've heard no rumor that
Philip has managed to dig his way out of this "real-life" thing that
swallowed him...
I know nothing about Philip, but according to the HISTORY file, the
last release was done 2 years ago. I think drastic measures should
be considered by moving to source over to something like savannah
or sourceforge so patches can be applied. The source is GPL'ed.
Whose ass do you have to light to get procmail development re-ignited?`
Also, I think there is something with older versions of namazu that
may cause problems (i.e. unexpected crashes during index creation
-- a reason I had to add namazu_cleanup() in web-archive). Therefore,
users should upgrade to 2.0.12, or later, if possible.
...
That's good to know. the NetBSD package system applied more
netbsd-specific patches than I'm comfortable mucking around with, but if
I start seeing problems, I will attempt to overcome that discomfort.
What are those netbsd-specific patches? Have the NetBSD developers
bothered to contact the Namazu developers about them?
* Your desire to put mbox files under the html directory was requested
by someone else some time back, I believe. I believe that user
found an alternative acceptable solution.
I think the idea of having more flexibility in the placement of
mbox files (and even html archives) on a per list basis can be
a useful, and very powerful, feature. Such a feature could be
driven by lists.def. For example:
Name: listname
Mbox-Archive-Path: /path/to/directory/for/listname/mbox/files
Html-Archive-Path: /path/to/directory/for/listname/html/archives
...
...
Putting the actual mboxes in the html directories makes me jumpy.
I agree, that is why I kept them separate, along with making the html
directory only contain files that would be indexed by namazu.
However, there could be some general uses of controling the location
of archive data. For example, it can be used to place archives
in different locations based on authentication access.
* Couldn't your symlinks to the mbox files be more like?:
$HTML_DIR/listname/mbox -> $MBOX_DIR/listname
I.e. In Perl code:
symlink("$MBOX_DIR/$list","$htmldir/mbox")
Wouldn't this disable the clunky URLs?:
http://example.com/mailman/private/listname/mbox/2003-09
Sure. It would also require a change to web-archive, because as
written, it expects $mbox_url to be
join('/', $MBOX_URL, $list, $mon);
Yep. I should consider on how to make this more flexible.
--ewh
---------------------------------------------------------------------
To sign-off this list, send email to majordomo(_at_)mhonarc(_dot_)org with the
message text UNSUBSCRIBE MHARC-USERS
