Re: [Scrollkeeper-devel] scrollkeeper problematic issues

[Ali A. <ali...@st...>]

Hello Dan,

> I'm sorry to hear this has given you so much grief.  I think I need to
> include some information about these problems in the INSTALL file, or
> possibly in a FAQ.

yeah this would seriously help understanding this much better.

> It sounds like most of your problems (1, 4, and 5) are caused by not
> having adequate docbook packages.  This is not surprising, because until
> recently the only place that good docbook packages could be found was in
> Red Hat mirrors.  This is because nobody used to use the XML catalogs, and
> so distributions didn't bother actually registering docbook in the
> catalogs.  Now that we are starting to use the catalog to do processing of
> DocBook/XML documents, we are in a painful period where docbook
> distributors need to fix their packages. To help things out, I made we
> made our own packages which you can use:
>
>      http://scrollkeeper.sourceforge.net/docbook.shtml
>
> If you use this package, you should not have to worry about things being
> installed in strange paths where they aren't found or the need to be
> connected to the internet to build.  (It tries to find the DTD on the
> internet, since the catalog is missing or incomplete, preventing it from
> finding the DTD on your own computer.)

yeah i know of that package you offering on your homepage, although i dont
fully agree to you by setting up the fact that my docbook installation isnt
correct. i am using the packages from the oasis homepage which comes with
default catalogfiles that imo looks quite ok to me.

neverthless by using your package there is one more issue lets say i install
gnome-xml then libxslt but after i reach the installation of libglade it go=
es
and overwrites the /etc/catalog file _ONCE_AGAIN_ this makes my point 5) of=
 my
previous email obsolete (the 2nd paragraph in it)

i would be happy to hear whats wrong with the default catalogfile. i am rea=
lly
worried using your own package and the createcatalog scripts. anyways i wou=
ld
really like to see a selfrunning scrollkeeper that dont touch my docbooks,
catalogs or whatever.

> For #2, I believe the package is working properly.  I don't think
> localstatedir is supposed to track prefix.  For example, on a vanilla
> Linux installation, prefix is /usr, localstatedir is /var, and sysconfdir
> is /etc.  Things which go under localstatedir belong in /var, not
> /usr/var.  Similarly, things which go under sysconfdir belong in /etc, not
> /usr/etc.  So, if somebody is doing something unusual, such as parallel
> installations, they should customize not only prefix but also sysconfdir
> and localstatedir.  I think a lot of people overlook this since most
> programs don't actually use sysconfdir and localstatedir and so for many
> packages customizing prefix alone is adequate.

well i am using a clean new linux installation without any previous
scrollkeeper installation, neverthless i am too long on unix and linux syst=
ems
to know what i am doing. before replying why dont you just grab your own
scrollkeeper 0.3.8 package make a simple

=2E/configure

only and see what it spits out at the end. the $(prefix) wont be resolved
correctly.

> #3 would definitely be breakage on the part of ScrollKeeper if it behaves
> as you describe it.  Would you mind double-checking that it is doing what
> you describe?  What do "scrollkeeper-config --localstatedir"  and
> "scrollkeeper-config --pkglocalstatedir" give you?  It is running the same
> commands the same way when you install ScrollKeeper and when you update
> the database when new GNOME packages are installed, so I can't see how it
> could change the directory.

bash-2.05a$ scrollkeeper-config --localstatedir
/usr/local/var
bash-2.05a$ scrollkeeper-config --pkglocalstatedir
/usr/local/var/lib/scrollkeeper
bash-2.05a$

thank you for your help.

=2D-=20
Name....: Ali Akcaagac
Status..: Student Of Computer & Economic Science
E-Mail..: mailto:ali...@st...
WWW.....: http://www.fh-wilhelmshaven.de/~akcaagaa