From: "Alfred M. Szmidt" <ams@kemisten.nu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: accessing own info files
Date: Fri, 17 Jan 2003 12:40:32 +0100 [thread overview]
Message-ID: <E18ZUrQ-0002jO-00@lgh163a.kemisten.nu> (raw)
In-Reply-To: <873cnskiyy.fsf@antithese.de> (message from Michael Below on Thu, 16 Jan 2003 20:11:49 +0100)
> What is the reason why Debian needs to keep a less "complete"
> version of install-info anyway (I don't care who was there
> first)?
It is a tool for automated installation of documentation for the
installed packages.
And the GNU version of install-info is what exactly? The automated
writting of documentation for installed packages? :-) Seriously, I do
not see any difference between GNU's version and Debian's version,
they both install/remove entries from $(infodir)/dir, only that they
do it a bit differently code wise, and option wise.
You give no reason on why Debian needs to keep a less featured version
of install-info that is also incompatible with GNU install-info, which
also is more widly used. Also, it is GNU texinfo that decides what
the dir file should look like, thus GNU's install-info is the
"upstream" version anyway.
next prev parent reply other threads:[~2003-01-17 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 12:59 accessing own info files Michael Below
2003-01-12 16:28 ` Benjamin Riefenstahl
2003-01-13 22:10 ` Michael Below
2003-01-14 7:17 ` Kai Großjohann
2003-01-14 15:36 ` Benjamin Riefenstahl
2003-01-14 17:14 ` Kai Großjohann
2003-01-15 1:09 ` Peter S Galbraith
2003-01-15 18:39 ` Benjamin Riefenstahl
2003-01-16 11:11 ` Alfred M. Szmidt
[not found] ` <mailman.367.1042715506.21513.help-gnu-emacs@gnu.org>
2003-01-16 15:43 ` Kai Großjohann
2003-01-16 17:04 ` Alfred M. Szmidt
[not found] ` <mailman.388.1042737292.21513.help-gnu-emacs@gnu.org>
2003-01-16 20:01 ` Kai Großjohann
2003-01-17 11:42 ` Alfred M. Szmidt
2003-01-16 19:11 ` Michael Below
2003-01-17 11:40 ` Alfred M. Szmidt [this message]
2003-01-13 3:16 ` Galen Boyer
2003-01-14 13:48 ` solution for " Michael Below
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18ZUrQ-0002jO-00@lgh163a.kemisten.nu \
--to=ams@kemisten.nu \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).