> Based on the messages above, I'd guess that you're running htdig version > 3.1.6. But the 3.1.x versions don't handle file:/ URLs, so unless the > KDevelop developers have patched htdig so it can, this doesn't make a lot > of sense to me.
Interesting that you say that htmerge ignores file:/ urls. Is it then possible to use htdig to index local docs at all? > > > The following files are created: > > db.docdb 14,6 MB > > db.docs.index 2,0 kb > > db.wordlist 18,9 MB > > db.words.db 19,3 MB > > > > Is this a problem because htdig is only indexing local files > (covered by the > > local_urls: file://localhost/=/ attribute) ?? > > No, but it would seem that htmerge is rejecting all the file:/ URLs that > it finds in db.docdb, so it ends up putting nothing into db.docs.index > (hence the small size, and the error above). htmerge can't tell whether > a given URL in the database was fetched via local_urls or not, as > it doesn't > look at that attribute nor the file system(s) referenced by it. > > Is it possible that your db.docdb was created by a 3.2.x beta of htdig? No, despite lots of experimenting I think I am still running a "vanilla" installation of htdig that I dled from here a few weeks ago. > This seems unlikely to me, but I can't see how else all those file:/ > URLs got in there otherwise (assuming vanilla htdig code). I have specifically entered the starting URL as file://usr/share/doc/kde/kdevelop/ etc etc in case that explains it. Maybe I should put in start URL as http://localhost/usr/share/doc/kde/kdevelop and let the local_urls: http://localhost/ = file:/// attribute handle the url covering - or have I misunderstood how the local_urls attribute works? >The other > possibility is that you're using a version of the ht://Dig 3.1.x package > in which htdig was patched to allow file:/ URLs, but the htmerge 3.1.6 > program you're using now hasn't been patched. If that's the case, where > are the patches for this? I don't recall seeing such a patch in the > standard patch archive at ftp.ccsf.org. No, I definitely have not fiddled around with patches - I've been too busy trying to get the vanilla version working to start getting clever ;-) I'll try the above mentioned attribute change and see of that makes any difference since you suggest that it may be because htmerge rejects file:// URLs. I'll report back if it works so that the thread at least has a happy ending. Thanks again, Richard Andrews _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
