On Tue, 29 Jan 2002, Geoff Hutchison wrote:
> I'm not sure why you'd want htmerge and not htpurge in this case (not
> to mention htdump and htload). I would think that in a library,
> you're less likely to need to merge whole databases together and more
> likely to want to delete URLs, etc.
According to Neal Richter:
> I sent a file called libhtdig-3.2.0.b4.tgz to Gilles and asked him
> to stick it in the 'contrib' directory.
OK, it's now in http://www.htdig.org/files/contrib/other/
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre
At 6:37 PM -0700 1/28/02, Neal Richter wrote:
>The libhtdig_htdig.cc is a callable replacement for the htdig executable.
>The libhtdig_htmerge.cc is a callable replacement for the htmerge executable.
I'm not sure why you'd want htmerge and not htpurge in this case (not
to mention htdump and htlo
Hey,
I sent a file called libhtdig-3.2.0.b4.tgz to Gilles and asked him
to stick it in the 'contrib' directory.
It's part of a larger project to restructure the code for these
goals:
1. All htdig code will be contained in the library
2. This library will be able to index data &
