From: Eli Zaretskii <eliz@gnu.org>
Cc: EmfoxZhou@gmail.com, emacs-devel@gnu.org, handa@m17n.org
Subject: Re: ./make-dist for unicode branch
Date: Thu, 26 Jan 2006 23:21:31 +0200 [thread overview]
Message-ID: <uk6cmeld0.fsf@gnu.org> (raw)
In-Reply-To: <E1F2BCl-00057X-JK@fencepost.gnu.org> (rms@gnu.org)
> From: "Richard M. Stallman" <rms@gnu.org>
> CC: eliz@gnu.org, EmfoxZhou@gmail.com, emacs-devel@gnu.org,
> miles@gnu.org
> Date: Thu, 26 Jan 2006 12:46:43 -0500
>
> If that is the rule, I don't mind removing uni-*.el from the
> CVS tree again. Richard, shall I?
>
> I was not following this discussion and I don't know what the issue is.
> Eli, could you summarize it?
First, this is about the unicode-2 branch, not about CVS HEAD.
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.)
Handa-san tried to fix this by checking the missing files into CVS,
but Miles objected, saying that generated files should not be there.
I think this is a non-issue, because make-dist is not supposed to
produce a workable tarball unless you bootstrap first. See
admin/make-tarball.txt, it explicitly says to bootstrap. As I see
this, a snapshot should be exactly like a release tarball, i.e. it
should include all the *.elc files etc. So one needs to build Emacs
before creating a snapshot.
So I don't think these files should be in CVS, and I don't think
there's any problem in make-dist. Rather, before creating a snapshot,
people should say "make bootstrap" in their sandbox.
next prev parent reply other threads:[~2006-01-26 21:21 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 [this message]
2006-01-27 0:49 ` Kenichi Handa
2006-01-27 7:23 ` Eli Zaretskii
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=uk6cmeld0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=EmfoxZhou@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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.