unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, eliz@is.elta.co.il,
	hattons@speakeasy.net, emacs-devel@gnu.org
Subject: Re: Emacs cvs newbie problems
Date: Tue, 01 Oct 2002 02:18:37 -0400	[thread overview]
Message-ID: <E17wGMf-0006lg-00@fencepost.gnu.org> (raw)
In-Reply-To: <200209301412.g8UECWC22730@f7.net> (karl@freefriends.org)

    Should Texinfo (and Emacs) install into /usr/share/info rather than /usr/info?

    Until now, the definition of $(infodir) has been $(prefix)/info, but 
    I gather we now will prefer $(datadir)/info.

Actually make-stds.texi already says it should be $(datarootdir)/info.
By default, both of them are, /usr/local/share/info.  However, 
If we want /usr/share/info, neither $(datadir) nor $(datarootdir)
will get us that.

    Another part of the problem is the plethora of dircategories that are in
    use.  Both the packagers and the maintainers tend to make up a new
    category at the drop of a hat, and this results in the same dir entries
    being repeated over and over again.

Would you like to develop a standard list of dircategory values?

  parent reply	other threads:[~2002-10-01  6:18 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 14:12 Emacs cvs newbie problems Karl Berry
2002-09-30 18:14 ` Eli Zaretskii
2002-10-01  6:18 ` Richard Stallman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-07 15:51 Karl Berry
2002-10-08 17:21 ` Richard Stallman
2002-10-07 15:51 Karl Berry
2002-10-07 16:09 ` Stefan Monnier
2002-10-04 15:57 Karl Berry
2002-10-05 16:33 ` Richard Stallman
2002-10-04 13:00 Karl Berry
2002-10-04 15:04 ` 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
2002-10-03 15:07 Karl Berry
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-03  0:32 ` Richard Stallman
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-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=E17wGMf-0006lg-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=hattons@speakeasy.net \
    --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).