From: Eli Zaretskii <eliz@gnu.org>
Cc: EmfoxZhou@gmail.com, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: ./make-dist for unicode branch
Date: Fri, 20 Jan 2006 12:53:20 +0200 [thread overview]
Message-ID: <uslrjqifz.fsf@gnu.org> (raw)
In-Reply-To: <E1Ezpn7-00014D-00@etlken> (message from Kenichi Handa on Fri, 20 Jan 2006 15:30:33 +0900)
> From: Kenichi Handa <handa@m17n.org>
> Date: Fri, 20 Jan 2006 15:30:33 +0900
> Cc: EmfoxZhou@gmail.com, emacs-devel@gnu.org
>
> In article <buor7735wc7.fsf@dhapc248.dev.necel.com>, Miles Bader <miles.bader@necel.com> writes:
>
> > Kenichi Handa <handa@m17n.org> writes:
> >> The files lisp/international/charprop.el and
> >> lisp/international/uni-*.el are generated by "make bootstrap" if there
> >> exists "admin" subdir. But, as they don't exist in CVS, your tarball
> >> doesn't contain them (nor 'admin' subdir).
> >>
> >> I vaguely remember that I have committed all those files
> >> once. I don't know why they don't exist in CVS now.
>
> > If they're automatically generated, they shouldn't be in CVS...
>
> I basically agree with that. But, then, how can we make
> them included in a tarball generated by Emfox's way?
What is the reason that those files are generated only if there's the
admin/ directory?
> Shuold we signal an error in make-dist when the directory is
> not yet readly for creating a tar ball? But it's not
> trivial to check if the directory is ready or not.
I think 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.
In other words, a snapshot is NOT simply a checked-out CVS tree, it's
a tarball like any release, except that it was made from a
non-released code base.
next prev parent reply other threads:[~2006-01-20 10:53 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 [this message]
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
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
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=uslrjqifz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=EmfoxZhou@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miles@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).