[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#52488: maint-guide can't be purged properly due to a .dhelp file


In <20000201135327.A11058@jagor.srce.hr>,
 at Date: Tue, 1 Feb 2000 13:53:27 +0100,
  on Subject: Re: Bug#52488: maint-guide can't be purged properly due to a  .dhelp file,
   Josip Rodin <jrodin@public.srce.hr> writes:

> This is dh_installdocs(1) problem, then, because I didn't manually edit
> my prerm.

I think many package including HTML docs using debhelper may have similar problem.

> > I think the required change is write the real location of the file
> > into /usr/share/doc-base/maint-guide.
> No, I can't do this. I did it once, and then it failed because of some
> dhelp thing (I won't claim that it's a problem - I don't care, I just
> know it didn't work).

Hmm. I did it now for my sgml-tools, so I wish to know if this does not work.

Current dhelp_parse can handle docs in FHS locations, and dhelp_parse_fsstnd
is provided for docs in FSSTND locations. And install-docs in doc-base uses
these in according to the location of docs specified by packages.

I think current dhelp can handle the docs in FHS locations, can't it ?

> I know I had to kludge around it (look at maint-guide-* postinsts).

I look at current postinst of maint-guide-ja. Is this the kludge ?

if [ "$1" = "configure" ]; then
  if [ -d /usr/doc -a ! -e /usr/doc/maint-guide -a -d /usr/share/doc/maint-guide
 ]; then
    ln -sf ../share/doc/maint-guide /usr/doc/maint-guide

Hmm. It seems that this kludge is required because the location of HTML files
is specified as FSSTND location in doc-base support. If dhelp can't handle
the documetns in FHS locations, then this is necessary.

Ah, I found that another problem if FSSTND location is specified by
doc-base support. (i.e. /usr/share/doc-base/<package>)

If the FSSTND location is specified for HTML docs, then install-docs
in doc-base use dhelp_parse_fsstnd instead of dhelp_parse.
But dhelp_parse_fsstnd seems not trace the link file.

Please try:

 BROWSER=lynx dhelp    (or "dhelp". I just like lynx to use)
     to check the maint-guide is shown in menu under debian/ title.

 sudo dhelp_parse_fsstnd -d /usr/doc/maint-guide/maint-guide.html/

   invoking "/usr/sbin/dhelp_parse_fsstnd" without argument shows:

      Usage: dhelp_parse <option> <directories>

         -a  add dhelp file in <directories>
         -d  del dhelp file in <directories>
         -r  index all dhelp files in /usr/doc

   so the use of dhelp_parse_fsstnd above should be right.

Then again,

 BROWSER=lynx dhelp

I can still read the title of maint-guide in the menu under debian/ dir.


 sudo dhelp_parse_fsstnd -r

does not give the result. maint-guide is still shown.

But "sudo dhelp_parse -d /usr/share/doc/maint-guide/maint-guide.html/"
does work instantly (without doing "dhelp_parse -r").

I suppose the specification of dhelp just changed from what you remember.

> Uh, I never made any complaint - if I need to fix something, of course
> I'll fix it. :)

I just found that doc-base support file in maint-guide and maint-guide-ja
 (i.e. /usr/share/doc-base/maint-guide(-ja)) has:

 | > Index: /usr/doc/maint-guide/maint-guide.html/index.en.html

  Format: HTML
  Index: /usr/doc/maint-guide/maint-guide.ja.html/index.ja.html
These ".en" and ".ja" are not the part of the real file name,
so I think you should remove these extra part when the real file name
is "index.html".

I don't know if there are some specification of debiandc2html, but
the current maint-guide has 


and maint-guide-ja has


So /usr/share/doc-base/maint-guide should specify

  Index: /usr/doc/maint-guide/maint-guide.html/index.html

at least, if you think FSSTND location should be there.

(I don't know what problem is coming when FHS location is specified here.
 I checked it locally, but I can't find the problem related to this.)

> Of course, if someone can tell me that /usr/share/doc should be used
> *safely* in those doc-base/dhelp files, I'll change it (in maint-guide* and
> libtiff3g-dev, other named packages aren't mine).

Please check the points I wrote above. Thanks.

  Taketoshi Sano: <sano@debian.org>,<sano@debian.or.jp>,<kgh12351@nifty.ne.jp>

Reply to: