According to richnat: > > 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?
In a roundabout way, yes, you can configure the 3.1.x versions of htdig to handle local docs. You almost answered your own question below. In the 3.2 betas, this is handled more elegantly, but the betas still have other problems of their own. > > 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. Where is "here"? Did you download htdig-3.1.6.tar.gz from http://www.htdig.org/files/? Have you ever downloaded and installed any other version of ht://Dig? > > 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? You're close. You can set local_urls: http://localhost/=/ (i.e. no space on either side of the "=", and no protocol spec. on the right hand side because a simple local path is assumed). That should do the trick, as long as htdig never has to fall back to HTTP - which means you have to stick to the limited set of file name extensions listed in http://www.htdig.org/attrs.html#local_urls, and you can't count on auto-indexing of "bare" directories with no index.html. > >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. What baffles me is the fact that htdig apparently didn't reject the file:/ URLs. Maybe I misunderstood the code. Upon closer inspection, it seems these URLs can slip through in start_url, but not in any hrefs it finds later. But when it comes to fetching these, they only work if they're http URLs or they're intercepted by local_urls. So, it would seem that you are meeting the requirements of local_urls, but if that's the case, it would be better to fake up some http:// URLs instead, so that they don't get rejected elsewhere. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) _______________________________________________ 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
