unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: $prefix/info -> $prefix/share/info
Date: Mon, 18 Dec 2006 22:21:54 +0200	[thread overview]
Message-ID: <uhcvtlztp.fsf@gnu.org> (raw)
In-Reply-To: <200612181447.57052.bruno@clisp.org> (message from Bruno Haible on Mon, 18 Dec 2006 14:47:56 +0100)

> From: Bruno Haible <bruno@clisp.org>
> Date: Mon, 18 Dec 2006 14:47:56 +0100
> 
> For several years already, the GNU coding standards and the Linux
> Filesystem Hierarchy Standard specify that 'info' files should be installed
> in $prefix/share/info rather than in $prefix/info. The rationale is and was
> that 'info' files are not platform dependent.
> 
> Since autoconf-2.60 was released 6 months ago, it is easy to actually
> implement this.
> 
> But Emacs-22.0.90 still installs into $prefix/info.
> 
> To follow the above cited standards, the following recipe can be used:
> 
> 1) Regenerate the 'configure' file with autoconf-2.60 or -2.61. An
> invocation of 'autoconf' is all that's needed.
> 
> 2) Apply this patch. I've verified that with this patch, Emacs installs its
> manuals into $prefix/share/info and that the info mode finds them there.
> 
> 
> 2006-12-17  Bruno Haible  <bruno@clisp.org>
> 
> 	* INSTALL: Mention /usr/local/share/info instead of /usr/local/info.
> 	* etc/emacs.1: Likewise.
> 	* src/epaths.in (PATH_INFO): Likewise.
> 	* nt/paths.h (PATH_INFO): Likewise.
> 	* lisp/paths.el (Info-default-directory-list): Put "share/" before "",
> 	before new info files will be installed in share/info.
> 	* lisp/info.el (Info-default-dirs): Look in $prefix/share/info instead
> 	of $prefix/info.
> 	* lisp/w32-fns.el (w32-init-info): Likewise.

Thanks, but the last change (to w32-fns.el) is not a good idea, since
invocation-directory there is not /usr/local/bin.  So GNU standards
are not applicable to the w32 case, and the patch to that file just
wastes disk space (by creating an unneeded directory) and lengthens
file names without any visible benefits.

I have no opinion about the rest of the change.

  reply	other threads:[~2006-12-18 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 13:47 $prefix/info -> $prefix/share/info Bruno Haible
2006-12-18 20:21 ` Eli Zaretskii [this message]
2006-12-20 14:24   ` Bruno Haible
2006-12-20 19:01     ` Eli Zaretskii
2006-12-20 13:01 ` Richard Stallman
2006-12-20 14:24   ` Bruno Haible
2006-12-25  0:43     ` Richard Stallman
2007-01-18 16:22       ` Chong Yidong

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=uhcvtlztp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).