unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: eliz@is.elta.co.il, miles@gnu.org, teirllm@dms.auburn.edu,
	hattons@speakeasy.net, emacs-devel@gnu.org
Subject: Re: Emacs cvs newbie problems
Date: Fri, 4 Oct 2002 09:00:32 -0400	[thread overview]
Message-ID: <200210041300.g94D0Wr10540@f7.net> (raw)

    If there happen to be multiple Info directories already, it doesn't
    matter tremendously which on a new file is installed in, 

It doesn't matter from the point of view of info (which is a problem in
itself, as Karl E. points out), but it may matter very much from the
point of view of the sysadmin.

For example, I know of sites that install emacs 21.2 into
/tools/emacs-21.2, completely.  This can ease upgrades, etc.  If
configure went ahead and installed the emacs 21.2 info files into
/usr/local/info, that would defeat the purpose.

    The existence of several Info directories is not a disaster, but it is
    somewhat of a problem.

I disagree.  When several info directories exist, that is usually
exactly what the installer/sysadmin wants to have.  Trying to make
configure outguess the local sysadmin seems quite wrong (not to mention
impossible) to me.

In my view, the simple infodir=$(datarootdir)/info default we have now
is not broken, in any way.  Instead of changing that, I suggest (once
again) that we simply fix the dir merging as we have discussed so that
redundant entries are not included.  That is what gave rise to the
original bug report and all the ensuing discussion -- not the existence
of multiple dir files.

             reply	other threads:[~2002-10-04 13:00 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 13:00 Karl Berry [this message]
2002-10-04 15:04 ` Emacs cvs newbie problems Stefan Monnier
2002-10-04 19:52 ` Eli Zaretskii
2002-10-05 16:33   ` Richard Stallman
2002-10-04 22:08 ` Richard Stallman
2002-10-04 22:28   ` Stefan Monnier
2002-10-06 16:14     ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-10-07 15:51 Karl Berry
2002-10-07 16:09 ` Stefan Monnier
2002-10-07 15:51 Karl Berry
2002-10-08 17:21 ` Richard Stallman
2002-10-04 15:57 Karl Berry
2002-10-05 16:33 ` Richard Stallman
2002-10-03 15:07 Karl Berry
2002-10-02 13:36 Karl Berry
2002-10-03  0:32 ` Richard Stallman
2002-10-02 13:36 Karl Berry
2002-10-03  0:33 ` Richard Stallman
2002-10-03  4:31   ` Eli Zaretskii
2002-10-04  3:48     ` Richard Stallman
2002-10-04 10:05   ` Karl Eichwalder
2002-10-04 15:46     ` Richard Stallman
2002-10-04 18:28       ` Karl Eichwalder
2002-10-05 16:33         ` Richard Stallman
2002-10-04 19:51     ` Eli Zaretskii
2002-10-02 13:36 Karl Berry
2002-10-02 20:31 ` Eli Zaretskii
2002-10-01 20:51 Karl Berry
2002-10-02  4:45 ` Eli Zaretskii
2002-10-01 20:07 Karl Berry
2002-10-01 20:15 ` Stefan Monnier
2002-10-02 19:23   ` Richard Stallman
2002-10-02  4:43 ` Eli Zaretskii
2002-10-01 17:24 Karl Berry
2002-10-01 18:18 ` Stefan Monnier
2002-10-01 14:13 Karl Berry
2002-10-01 14:41 ` Stefan Monnier
2002-10-02  4:07   ` Richard Stallman
2002-10-02  4:07 ` Richard Stallman
2002-10-01 14:13 Karl Berry
2002-10-01 18:16 ` Eli Zaretskii
2002-10-01 18:42   ` Stefan Monnier
2002-10-02  4:41     ` Eli Zaretskii
2002-10-02  4:07 ` Richard Stallman
2002-10-01 14:13 Karl Berry
2002-10-02  4:07 ` Richard Stallman
2002-09-30 21:43 Karl Berry
2002-10-01  4:40 ` Eli Zaretskii
2002-09-30 14:12 Karl Berry
2002-09-30 18:14 ` Eli Zaretskii
2002-10-01  6:18 ` Richard Stallman
2002-09-16 21:07 Karl Berry
2002-09-16  0:02 Karl Berry
2002-09-16  1:41 ` Miles Bader
2002-09-16  2:14   ` Alan Shutko
2002-09-16  5:40     ` Rob Browning
2002-09-18 18:46       ` Eli Zaretskii
2002-09-16  1:51 ` Steven T. Hatton
2002-09-16 19:28 ` Richard Stallman
2002-09-18 18:44   ` Eli Zaretskii
2002-09-20  3:09     ` Luc Teirlinck
2002-09-20  4:45       ` Miles Bader
2002-09-20 18:42       ` Richard Stallman
2002-09-20 21:21         ` Eli Zaretskii
2002-09-20 21:28       ` Eli Zaretskii
2002-09-20 22:07         ` Luc Teirlinck
2002-09-20 22:41           ` Luc Teirlinck
2002-09-21  8:27           ` Eli Zaretskii
2002-09-21 19:39           ` Richard Stallman
2002-09-21 22:13             ` Luc Teirlinck
2002-09-22  4:49               ` Eli Zaretskii
2002-09-30  2:49               ` Richard Stallman
2002-09-30  3:40                 ` Luc Teirlinck
2002-09-30  5:32                   ` Eli Zaretskii
2002-10-01  6:17                   ` Richard Stallman
2002-10-01  7:49                     ` Miles Bader
2002-09-20 22:19         ` Luc Teirlinck
2002-09-14 20:40 Steven T. Hatton
2002-09-14 21:12 ` Luc Teirlinck
2002-09-14 22:11   ` Steven T. Hatton
2002-09-14 23:03     ` Luc Teirlinck
2002-09-15  1:24       ` Steven T. Hatton
2002-09-15  2:42         ` Luc Teirlinck
2002-09-15 11:13           ` Steven T. Hatton
2002-09-15 12:42         ` Miles Bader
2002-09-15 20:50         ` Richard Stallman
2002-09-15 20:50         ` Richard Stallman
2002-09-15  0:08     ` Luc Teirlinck
2002-09-15 20:50       ` Richard Stallman
2002-09-15 15:37     ` Luc Teirlinck
2002-09-15 15:16 ` Kai Großjohann
2002-09-14  6:20 Steven T. Hatton
2002-09-14  6:40 ` Damien Elmes
2002-09-15  1:50 ` Richard Stallman

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=200210041300.g94D0Wr10540@f7.net \
    --to=karl@freefriends.org \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=hattons@speakeasy.net \
    --cc=miles@gnu.org \
    --cc=teirllm@dms.auburn.edu \
    /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).