Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Debian's install-info
Date: Tue, 23 Mar 2004 11:10:30 +0900	[thread overview]
Message-ID: <b9y3c80b9ex.fsf@jpl.org> (raw)
In-Reply-To: <m38yhsxvde.fsf@defun.localdomain>

>>>>> In <m38yhsxvde.fsf@defun.localdomain>
>>>>>	Jesper Harder <harder@ifa.au.dk> wrote:

> The newest version of automake/autoconf still produces something equivalent:

> @if (install-info --version && \
>      install-info --version 2>&1 | sed 1q | grep -i -v debian) >/dev/null 2>&1; then \

> for a new project, so presumeably there is still a need for it.  I
> don't know why, though.

Thanks.  I also found many packages exclude Debian's install-info,
and what should be mentioned specially is the following ChangeLog
entry in glibc-2.3.2:

1997-07-15  Marcus G. Daniels  <marcus@cathcart.sysc.pdx.edu>

	* manual/Makefile (INSTALL_INFO): Introduce variable to override
	path to install-info for systems like Debian that have an
	install-info with a different command line interface from the
	canonical GNU texinfo version.

According to the manual/Makefile file, it seems necessary to
specify the section name to Debian's install-info program like:

install-info --info-dir=DIR --section '^Gnus:' 'Gnus:' ./gnus

Although Artiom Neganov wrote that the present install-info of
Debian works with the same command line arguments as the GNU
version, I leave the solution to Debian maintainers since I'm
not a Debian user.

;; I'll forward this message to Artiom Neganov and the emacs-w3m
;; list.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



  reply	other threads:[~2004-03-23  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 23:26 Katsumi Yamaoka
2004-03-23  0:25 ` Jesper Harder
2004-03-23  2:10   ` Katsumi Yamaoka [this message]
2004-03-23  1:54 ` Alan Shutko
2004-03-24  8:33   ` Kai Grossjohann
2004-05-16 14:30     ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b9y3c80b9ex.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).