Mercurial > emacs
view admin/make-tarball.txt @ 49667:cbec1327e2f1
(QCfilter_multibyte): New variable.
(setup_process_coding_systems): New function.
(Fset_process_buffer, Fset_process_filter): Call
setup_process_coding_systems.
(Fstart_process): Initialize the member `filter_multibyte' of
struct Lisp_Process.
(create_process): Call setup_process_coding_systems.
(Fmake_network_process): New keyward `:filter-multibyte'.
Initialize the member `filter_multibyte' of struct Lisp_Process.
Call setup_process_coding_systems.
(server_accept_connection): Call setup_process_coding_systems.
(read_process_output): If the process has a filter, decide the
multibyteness of a string to given to the filter by
`filter_multibyte' member of the process. If the process doesn't
have a filter and the result of conversion is unibyte, use
Fstring_to_multibyte (not Fstring_make_multibyte) to get the
multibyte form.
(Fset_process_coding_system): Call setup_process_coding_systems.
(Fset_process_filter_multibyte): New function.
(Fprocess_filter_multibyte_p): New function.
(syms_of_process): Intern and staticpro QCfilter_multibyte.
Defsubr Sset_process_filter_multibyte and
Sprocess_filter_multibyte_p.
author | Kenichi Handa <handa@m17n.org> |
---|---|
date | Mon, 10 Feb 2003 07:58:29 +0000 |
parents | aaac2b2bb2d1 |
children | d0449a23c8d9 d7ddb3e565de |
line wrap: on
line source
Instructions to create pretest or release tarballs. -- originally written by Eli Zaretskii, amended by Francesco Potort́ For each step, check for possible errors. 1. cvs -q update -Pd 2. Bootstrap to make 100% sure all elc files are up-to-date, and to make sure that the later tagged version will bootstrap, should it be necessary to check it out. 3. Set the version number (M-x load-file RET admin/admin.el RET, then M-x set-version RET). For a release, add released change log entries (M-x add-release-logs RET). 4. rm configure; make bootstrap 5. Commit configure, README, lisp/loaddefs.el, lisp/cus-load.el, lisp/finder-inf.el, lisp/version.el, man/emacs.texi. For a release, also commit the ChangeLog files in all directories. 6. make-dist --snapshot. Check the contents of the new tar with admin/diff-tar-files against an older tar file. Some old pretest tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/, while old emacs tarballs are at <ftp://ftp.gnu.org/pub/gnu/emacs/>. 7. xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta 8. tar -zxf emacs-NEW.tar.gz; cd emacs-NEW configure && make && make -n install Use `script' or M-x compile to save the compilation log in compile-NEW.log and compare it against an old one. The easiest way to do that is to visit the old log in Emacs, change the version number of the old Emacs to __, do the same with the new log and do M-x ediff. Especially check that Info files aren't built. 9. cd EMACS_ROOT_DIR; cvs tag TAG TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest, EMACS_XX_YY for a release. 10. admin/make-announcement OLD NEW This creates an announcement for pretests. OLD is the version used to make deltas with respect to NEW. *release instructions missing* 11. For a pretest, do: rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta compile-NEW.log \ emacs-NEW.announce alpha.gnu.org:/home/alpha/gnu/emacs/pretest/. *release instructions missing* 12. Verify that after five minutes at most the files appear on ftp://alpha.gnu.org/gnu/emacs/pretest/. *release instructions missing* 13. Let Richard Stallman know about the new pretest and tell him to announce it using the announcement you prepared. Remind him to set a Reply-to header to <emacs-pretest-bug@gnu.org>. *release instructions missing*