unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: rms@gnu.org
Cc: Ken Raeburn <raeburn@raeburn.org>, Kenichi Handa <handa@m17n.org>,
	emacs-devel@gnu.org
Subject: Re: minor observations on Mac build of 22.0.99
Date: Mon, 30 Apr 2007 21:04:52 -0400	[thread overview]
Message-ID: <n2odl5tkuj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1Hie4b-0002Bp-MS@fencepost.gnu.org> (Richard Stallman's message of "Mon, 30 Apr 2007 18:10:21 -0400")

Richard Stallman wrote:

>     Are these files in fact going to be identical aside from the date  
>     stamp in all builds?  If so, perhaps like the .elc files in the lisp  
>     tree they should be pre-generated for the release and pretest  
>     distributions.
>
> They definitely should be.  I did not realize this was not already the
> case.  Can someone please fix this and ack?

It's not apparent from what you quote, but you do know this refers to
only a small number of files in the leim/quail directory, right? The
associated .el files are not even included with an Emacs tarball at
present, because they are generated from various dictionary files at
build time.

I don't know if there is any reason for this besides space-saving, but
it was not considered a problem two years ago:

emacs-devel, 2005/04/13, "make-dist doesn't distribute some quail files"
http://lists.gnu.org/archive/html/emacs-devel/2005-04/msg00475.html

  reply	other threads:[~2007-05-01  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30  6:56 minor observations on Mac build of 22.0.99 Ken Raeburn
2007-04-30 10:25 ` Andreas Schwab
2007-04-30 19:25   ` Ken Raeburn
2007-04-30 19:41     ` Andreas Schwab
2007-04-30 22:10 ` Richard Stallman
2007-05-01  1:04   ` Glenn Morris [this message]
2007-05-01 10:58     ` Ken Raeburn
2007-05-02  4:39     ` Richard Stallman
2007-05-02  1:39   ` Glenn Morris

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=n2odl5tkuj.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=raeburn@raeburn.org \
    --cc=rms@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).