htdig w/ 1.4 vs. 2.0
Ralf Nolden
nolden at kde.org
Tue Aug 28 09:22:13 BST 2001
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
-------------- next part --------------
#=======================================================================
#
# Example config file for ht://Dig.
#
# This configuration file is used by all the programs that make up ht://Dig.
# Please refer to the attribute reference manual for more details on what
# can be put into this file. (http://www.htdig.org/confindex.html)
# Note that most attributes have very reasonable default values so you
# really only have to add attributes here if you want to change the defaults.
#
# What follows are some of the common attributes you might want to change.
#
#
# Specify where the database files need to go. Make sure that there is
# plenty of free disk space available for the databases. They can get
# pretty big.
#
database_dir: /var/lib/kdevelop
#
# This specifies the URL where the robot (htdig) will start. You can specify
# multiple URLs here. Just separate them by some whitespace.
# The example here will cause the ht://Dig homepage and related pages to be
# indexed.
# You could also index all the URLs in a file like so:
# start_url: `${common_dir}/start.url`
#
start_url: file://localhost//usr/share/doc/KDE_API
file://localhost//usr/lib/qt2/html
file://localhost//usr/lib/qt2/tutorial
#http://localhost/
#http://www.htdig.org/
#
# This attribute limits the scope of the indexing process. The default is to
# set it to the same as the start_url above. This way only pages that are on
# the sites specified in the start_url attribute will be indexed and it will
# reject any URLs that go outside of those sites.
#
# Keep in mind that the value for this attribute is just a list of string
# patterns. As long as URLs contain at least one of the patterns it will be
# seen as part of the scope of the index.
#
limit_urls_to: file://
#${start_url}
#
# If there are particular pages that you definately do NOT want to index, you
# can use the exclude_urls attribute. The value is a list of string patterns.
# If a URL matches any of the patterns, it will NOT be indexed. This is
# useful to exclude things like virtual web trees or database accesses. By
# default, all CGI URLs will be excluded. (Note that the /cgi-bin/ convention
# may not work on your web server. Check the path prefix used on your web
# server.)
#
exclude_urls: /cgi-bin/ .cgi
#
# The string htdig will send in every request to identify the robot. Change
# this to your email address.
#
maintainer: root at localhost
#
# The excerpts that are displayed in long results rely on stored information
# in the index databases. The compiled default only stores 512 characters of
# text from each document (this excludes any HTML markup...) If you plan on
# using the excerpts you probably want to make this larger. The only concern
# here is that more disk space is going to be needed to store the additional
# information. Since disk space is cheap (! :-)) you might want to set this
# to a value so that a large percentage of the documents that you are going
# to be indexing are stored completely in the database. At SDSU we found
# that by setting this value to about 50k the index would get 97% of all
# documents completely and only 3% was cut off at 50k. You probably want to
# experiment with this value.
# Note that if you want to set this value low, you probably want to set the
# excerpt_show_top attribute to false so that the top excerpt_length characters
# of the document are always shown.
#
max_head_length: 10000
#
# To limit network connections, ht://Dig will only pull up to a certain limit
# of bytes. This prevents the indexing from dying because the server keeps
# sending information. However, several FAQs happen because people have files
# bigger than the default limit of 100KB. This sets the default a bit higher.
# (see <http://www.htdig.org/FAQ.html> for more)
#
max_doc_size: 200000
#
# Depending on your needs, you might want to enable some of the fuzzy search
# algorithms. There are several to choose from and you can use them in any
# combination you feel comfortable with. Each algorithm will get a weight
# assigned to it so that in combinations of algorithms, certain algorithms get
# preference over others. Note that the weights only affect the ranking of
# the results, not the actual searching.
# The available algorithms are:
# exact
# endings
# synonyms
# soundex
# metaphone
# By default only the "exact" algorithm is used with weight 1.
# Note that if you are going to use any of the algorithms other than "exact",
# you need to use the htfuzzy program to generate the databases that each
# algorithm requires.
#
search_algorithm: exact:1 synonyms:0.5 endings:0.1
common_dir: /opt/kde2/share/apps/kdevelop/htdig/common
maximum_pages: 1
ignore_noindex: true
#
# The following are the templates used in the builtin search results
# The default is to use compiled versions of these files, which produces
# slightly faster results. However, uncommenting these lines makes it
# very easy to change the format of search results.
# See <http://www.htdig.org/hts_templates.html for more details.
#
# template_map: Long long ${common_dir}/long.html \
# template_name: long
#
# The following are used to change the text for the page index.
# The defaults are just boring text numbers. These images spice
# up the result pages quite a bit. (Feel free to do whatever, though)
#
next_page_text: <img src=/opt/www/htdocs/htdig/buttonr.png border=0 align=middle width=30 height=30 alt=next>
no_next_page_text:
prev_page_text: <img src=/opt/www/htdocs/htdig/buttonl.png border=0 align=middle width=30 height=30 alt=prev>
no_prev_page_text:
page_number_text: "<img src=/opt/www/htdocs/htdig/button1.gif border=0 align=middle width=30 height=30 alt=1>" \
"<img src=/opt/www/htdocs/htdig/button2.png border=0 align=middle width=30 height=30 alt=2>" \
"<img src=/htdig/button3.gif border=0 align=middle width=30 height=30 alt=3>" \
"<img src=/htdig/button4.gif border=0 align=middle width=30 height=30 alt=4>" \
"<img src=/htdig/button5.gif border=0 align=middle width=30 height=30 alt=5>" \
"<img src=/htdig/button6.gif border=0 align=middle width=30 height=30 alt=6>" \
"<img src=/htdig/button7.gif border=0 align=middle width=30 height=30 alt=7>" \
"<img src=/htdig/button8.gif border=0 align=middle width=30 height=30 alt=8>" \
"<img src=/htdig/button9.gif border=0 align=middle width=30 height=30 alt=9>" \
"<img src=/htdig/button10.gif border=0 align=middle width=30 height=30 alt=10>"
#
# To make the current page stand out, we will put a border arround the
# image for that page.
#
no_page_number_text: "<img src=/opt/www/htdocs/htdig/button1.png border=2 align=middle width=30 height=30 alt=1>" \
"<img src=/htdig/button2.gif border=2 align=middle width=30 height=30 alt=2>" \
"<img src=/htdig/button3.gif border=2 align=middle width=30 height=30 alt=3>" \
"<img src=/htdig/button4.gif border=2 align=middle width=30 height=30 alt=4>" \
"<img src=/htdig/button5.gif border=2 align=middle width=30 height=30 alt=5>" \
"<img src=/htdig/button6.gif border=2 align=middle width=30 height=30 alt=6>" \
"<img src=/htdig/button7.gif border=2 align=middle width=30 height=30 alt=7>" \
"<img src=/htdig/button8.gif border=2 align=middle width=30 height=30 alt=8>" \
"<img src=/htdig/button9.gif border=2 align=middle width=30 height=30 alt=9>" \
"<img src=/htdig/button10.gif border=2 align=middle width=30 height=30 alt=10>"
star_image: file://localhost//opt/kde2/share/apps/kdevelop/htdig/common/kde_star.png
star_blank: file://localhost/opt/www/htdocs/htdig/star_blank.png
script_name: file://usr/local/httpd/cgi-bin/htsearch
local_urls_only: true
# local variables:
local_urls: file://localhost=
#local_urls: file://=
# mode: text
# eval: (if (eq window-system 'x) (progn (setq font-lock-keywords (list '("^#.*" . font-lock-keyword-face) '("^[a-zA-Z][^ :]+" . font-lock-funct
# end:
More information about the KDevelop
mailing list