On Tue, 2008-06-24 at 23:58 +0200, Esteban Manchado Velázquez wrote: > Hi, > > The stacktrace seems to be some problem in some doc-base files. I have > made dhelp more robust to that, and now it handles those without complaining. > I have just uploaded 0.6.10 fixing that. > > However, I'm not sure that's the problem you're experiencing. What is > happening there is that when you register some documentation in dhelp, it > indexes the contents so you can search for it. In some cases that can mean > indexing a lot of documentation (in some upgrade with many packages, where > install-docs calls dhelp_parse with many packages at once). So it's expected > behaviour that many index++ processes are spawned. Are you saying that if I had let it run long enough, it would have finished? I think I gave it at least 10 minutes, and it definitely was way longer than I've encountered before. > > Of course, one might argue that in those cases you prefer not indexing at > all, or maybe indexing in the background, but I'm not completely sure how to > handle the situation. Maybe only index when registering a single document? > Maybe disable the indexing on install completely, and only index weekly? I > don't like that very much because it means that when you install some package, > you can't search for its documentation until the next week (and I guess you're > likely to want to search for the documentation of a package a couple of days > after installing it). I know I often install documentation when I discover I need it, so indexing it later wouldn't help much. On the other hand, I'm not sure what's being indexed. I don't use dhelp that I'm aware of, and I always have to reindex man pages manually after installing new ones.
Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
