htdig w/ 1.4 vs. 2.0

Steven Suson suson at TuckerEnergy.com
Fri Sep 7 01:18:58 BST 2001


Ralf,

    I apologize for taking so long to get back to you on this one. I'm on a
deadline crunch, and having other KDevelop problems as well (see the last email
I posted). But I'm finally back to report my latest results.

    I tried the htdig.conf that you sent, with the appropriate modifications,
and was not able to get it to index at all. Results like it telling me it could
not find the files (that it named, meaning that it found them in some sense
anyway). So I decided to bite the bullet, and go back to the README.htdig, and
follow ALL the instructions quite carefully. I even generated a new patch for
the noindex business (patch referenced would no longer apply), built, and
installed a new htdig RPM. Modified the htdig.conf as indicated, and all of the
htdig "common" files. After all this, it still (for whatever reason) INSISTED on
attempting to index my kernel source tree (/usr/src/linux), without indexing my
Qt and KDE. Frustrated, but undaunted, I renamed /usr/src/linux to
/usr/src/linux_DONTSEARCHME, and with this combined w/ unchecking index Qt, and
index KDE, AND adding those paths as extra paths to index, I finally got htdig
to build its database...

    Yet, after all that, attempting to use any search documentation
functionality within KDevelop yields nothing more than the message in the status
bar, something like "Searching for text within documentation..."

    Needless to say, at this point, I'm both dazed and confused. Incidentally, I
noticed that left over from my 1.4 usage, that there was an htdig db directory
("~/KDevelop-doc", I believe) in my home directory. I'm not sure as to the
nature of the change(s) that have brought about all this, and perhaps it is not
my place to say, but I for one preferred the old way...

TIA,
Steven Suson
"Keep the faith."

Ralf Nolden wrote:

> On Montag, 27. August 2001 23:39, you wrote:
>
> Steven,
>
> things don't have to bee too complicated :) The README.htdig is just giving
> the general idea with covering the exceptions for different htdig versions.
> Usually it works unpatched, as on SuSE since a while now. So if you managed
> to install 1.4 and run that ok with the search indexing, and your RH package
> for 2.0 misses that configuration, then just install 1.4 and put 2.0 over it.
> If the 1.4 package worked for you, 2.0 should do as well. For convenience I
> added my htdig.conf file that's provided for SuSE on their package (they care
> about a flawless install of kdevelop, so does Caldera AFAIK) that can help
> you solve your problems. Basically you probably only need to change the path
> to your KDE installation that on SuSE is /opt/kde2.
>
> Ralf
> > Hi Ralf,
> >
> >     Thanks for the response; hope this finds you doing well.
> >
> >     First of all, perhaps a little background information is in order:
> >
> >         Red Hat 7.1
> >         XFree86 4.0.3
> >         Kernel 2.4.7
> >         KDE 2.2
> >
> >      KDevelop 1.4 gave me my first experience of a totally flawless
> > indexing and use of the documentation; always in the past there where
> > little (and generally well known) glitches, but it was possible to work
> > around them. I have changed nothing whatsoever, but the behavior is
> > completely different. First it could not find the htdig.conf. Browsing the
> > code ("Use the source, Luke"), I discovered that it was looking in
> > /usr/share/apps/kdevelop/tools. From here I wondered onto the README.htdig,
> > and became sort of shocked.... It spoke of installing several files under
> > this directory, of patch htdig (!), adding completely new options to the
> > htdig.conf file, etc... When I attempted to follow all of these
> > instructions (except the patch part), it appeared to index my qt docs, and
> > for whatever reason, /usr/src/linux/include???? And.... no KDE docs
> > indexed.
> >
> >     When I get back on this, I'll send you some of the output.
> >
> > Thanks,
> > Steven Suson
> > "Keep the faith."
> >
> > Ralf Nolden wrote:
> > > On Montag, 27. August 2001 21:46, you wrote:
> > >
> > > Hi Steven,
> > >
> > > though I don't know what your exact problem is, the htdig at least on
> > > SuSE works fine here. We did have a little change during the 2.0
> > > development there but it surely should work with your htdig.conf file.
> > > The problem with htdig's only root access is that the database is located
> > > in the area on the filesystem where only root has access. I'm no htdig
> > > expert so I can't tell for sure what's going on but I think KDE has had
> > > problems with htdig in the helpcenter as well if you want to go for
> > > htdig's full capacity. Please let us know which problems you have exactly
> > > so we could gather a little group that could take care about those issues
> > > and simplify them for 3.0; if there is something known not working due to
> > > the kdevelop code we can influence, then we can fix up 2.0 before it
> > > ships as 2.0.1 with KDE 2.2.1 :)
> > >
> > > Thanks for the info anyway,
> > >
> > > Ralf
> > >
> > > > Greetings all,
> > > >
> > > >     I am somewhat at a loss. With kdevelop 1.4, I had to nothing
> > > > whatsoever to htdig. Now w/ 2.0, I have a complicated list of
> > > > modifications, including even the apparent necessity of patching htdig.
> > > > Not only that, it is not readily apparent to me how a user might have
> > > > his own "private" htdig database, and thus only root will be able to
> > > > maintain the htdig db (indexing new things). My biggest puzzle is why
> > > > it got harder, rather than easier.
> > > >
> > > >     One way or another I must resolve this. Once I've done so, I'll
> > > > probably package (RPM) up something like "kdevelop-htdig". Has anyone
> > > > done something like this already? Any guidance, etc. would be much
> > > > appreciated.
> > > >
> > > > TIA,
> > > > Steven Suson
> > > > "Keep the faith."
> > > >
> > > >
> > > > -
> > > > to unsubscribe from this list send an email to
> > > > kdevelop-request at kdevelop.org with the following body: unsubscribe
> > > > »your-email-address«
> > >
> > > --
> > > We're not a company, we just produce better code at less costs.
> > > --------------------------------------------------------------------
> > > Ralf Nolden
> > > nolden at kde.org
> > >
> > > The K Desktop Environment       The KDevelop Project
> > > http://www.kde.org              http://www.kdevelop.org
> > >
> > > -
> > > to unsubscribe from this list send an email to
> > > kdevelop-request at kdevelop.org with the following body: unsubscribe
> > > »your-email-address«
> >
> > -
> > to unsubscribe from this list send an email to
> > kdevelop-request at kdevelop.org with the following body: unsubscribe
> > »your-email-address«
>
> --
> We're not a company, we just produce better code at less costs.
> --------------------------------------------------------------------
> Ralf Nolden
> nolden at kde.org
>
> The K Desktop Environment       The KDevelop Project
> http://www.kde.org              http://www.kdevelop.org
>
>   ------------------------------------------------------------------------
>                  Name: htdig.conf
>    htdig.conf    Type: Plain Text (text/plain)
>              Encoding: base64


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop mailing list