From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, EmfoxZhou@gmail.com
Subject: Re: ./make-dist for unicode branch
Date: Fri, 27 Jan 2006 09:23:53 +0200 [thread overview]
Message-ID: <uhd7qdth2.fsf@gnu.org> (raw)
In-Reply-To: <E1F2HoD-0003O9-00@etlken> (message from Kenichi Handa on Fri, 27 Jan 2006 09:49:49 +0900)
> From: Kenichi Handa <handa@m17n.org>
> CC: rms@gnu.org, EmfoxZhou@gmail.com, emacs-devel@gnu.org
> Date: Fri, 27 Jan 2006 09:49:49 +0900
>
> > The problem is that a tarball created with "make-dist --snapshot" out
> > of a freshly checked-out CVS unicode-2 branch tree would not build
> > because the files lisp/international/charprop.el and
> > lisp/international/uni-*.el are generated by "make bootstrap" only if
> > there's the `admin' subdirectory. (I asked why it looks for that
> > directory, but didn't see any answers.)
>
> Ah, sorry for forgetting to answer it. The reason is that
> those files are generated from
> admin/unidata/UnicodeData.txt. This file is about 1M byte,
> so I thought it was too big to be included in a tarball.
> The total of generated uni-*.el is about 200K.
It's too early to discuss the packaging of Emacs 23, but I'd say
UnicodeData.txt _should_ be part of the tarball, because otherwise
users will not be able to regenerate those *.el files if they want
to change some of the characters' attributes. 800KB more is not going
to change anything in what is already a 80MB to 130MB source tree.
> I didn't know about admin/make-tarball.txt. Now I agree
> that we don't have to put uni-*.el in CVS tree. Perhaps, we
> should add a comment about the requirement of bootstrap at
> somewhere in make-dist.
Even better, perhaps make-dist should find some way to check whether a
bootstrap was done, and refuse to work if it wasn't.
next prev parent reply other threads:[~2006-01-27 7:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:43 ./make-dist for unicode branch Emfox Zhou
2006-01-17 19:56 ` Eli Zaretskii
2006-01-17 22:08 ` Emfox Zhou
2006-01-18 0:41 ` Kenichi Handa
2006-01-18 3:38 ` Emfox Zhou
2006-01-19 11:35 ` Kenichi Handa
2006-01-19 19:05 ` Emfox Zhou
2006-01-20 4:50 ` Kenichi Handa
2006-01-20 4:58 ` Miles Bader
2006-01-20 6:30 ` Kenichi Handa
2006-01-20 6:56 ` Miles Bader
2006-01-20 10:53 ` Eli Zaretskii
2006-01-26 1:09 ` Kenichi Handa
2006-01-26 17:46 ` Richard M. Stallman
2006-01-26 21:21 ` Eli Zaretskii
2006-01-27 0:49 ` Kenichi Handa
2006-01-27 7:23 ` Eli Zaretskii [this message]
2006-01-27 7:47 ` Kenichi Handa
2006-01-28 4:50 ` Richard M. Stallman
2006-01-29 12:11 ` Kenichi Handa
2006-01-30 0:57 ` Richard M. Stallman
2006-01-30 12:32 ` Kenichi Handa
2006-01-30 19:23 ` Eli Zaretskii
2006-01-31 1:08 ` Kenichi Handa
2006-01-31 1:51 ` Miles Bader
2006-01-31 18:04 ` Richard M. Stallman
2006-01-27 22:32 ` Richard M. Stallman
2006-01-20 6:13 ` Emfox Zhou
2006-01-20 10:11 ` Zhang Wei
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uhd7qdth2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=EmfoxZhou@gmail.com \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.