From: Ken Raeburn <raeburn@raeburn.org>
To: emacs-devel@gnu.org
Subject: minor observations on Mac build of 22.0.99
Date: Mon, 30 Apr 2007 02:56:43 -0400 [thread overview]
Message-ID: <914DA7BD-35E5-45AC-BC42-38FA55FBBA60@raeburn.org> (raw)
I grabbed the 22.0.99 pretest and built it on a couple of Macs, one
PPC and one Intel. Both builds went just fine, and Emacs installs
and (so far) runs fine as well.
A couple observations, neither of which seems critical to address for
the release:
1) The installer adds files to /Applications/Emacs.app if it already
exists, rather than replacing that tree completely. On one of my
machines, /Applications/Emacs.app/Contents/MacOS/bin now contains
both emacs-22.0.91 and emacs-22.0.99. If I move Emacs.app to the
trash before installing, the result is cleaner, with just
emacs-22.0.99. (Similarly for other files: the old DOC file, some
elisp and image files, etc., were left over from the old version.)
Is this intentional or expected, or a bug?
2) Out of curiosity, I compared the Intel and PPC trees with diff.
Not only were the executables different, which was expected of
course, but also leim/quail had differences in the .el.gz and .elc
files. Picking a .el.gz file at random, the only difference I found
was in the date stamp.
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.
Ken
next reply other threads:[~2007-04-30 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 6:56 Ken Raeburn [this message]
2007-04-30 10:25 ` minor observations on Mac build of 22.0.99 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
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=914DA7BD-35E5-45AC-BC42-38FA55FBBA60@raeburn.org \
--to=raeburn@raeburn.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).