admin/make-tarball.txt

   1 Instructions to create pretest or release tarballs.
   2 -- originally written by Eli Zaretskii, amended by Francesco Potortì
   3
   4 For each step, check for possible errors.
   5
   6 1.  cvs -q update -Pd
   7
   8 2.  Bootstrap to make 100% sure all elc files are up-to-date, and to
   9     make sure that the later tagged version will bootstrap, should it be
  10     necessary to check it out.
  11
  12 3.  Set the version number (M-x load-file RET admin/admin.el RET, then
  13     M-x set-version RET).  For a release, add released change log
  14     entries (M-x add-release-logs RET).
  15
  16 4.  rm configure; make bootstrap
  17
  18 5.  Commit configure, README, lisp/loaddefs.el, lisp/cus-load.el,
  19     lisp/finder-inf.el, lisp/version.el, man/emacs.texi.  For a release,
  20     also commit the ChangeLog files in all directories.
  21
  22 6.  make-dist --snapshot.  Check the contents of the new tar with
  23     admin/diff-tar-files against an older tar file.  Some old pretest
  24     tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/, while
  25     old emacs tarballs are at <ftp://ftp.gnu.org/pub/gnu/emacs/>.
  26
  27 7.  xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta
  28
  29 8.  tar -zxf emacs-NEW.tar.gz; cd emacs-NEW
  30     configure && make && make -n install
  31     Use `script' or M-x compile to save the compilation log in
  32     compile-NEW.log and compare it against an old one.  The easiest way
  33     to do that is to visit the old log in Emacs, change the version
  34     number of the old Emacs to __, do the same with the new log and do
  35     M-x ediff. Especially check that Info files aren't built.
  36
  37 9.  cd EMACS_ROOT_DIR; cvs tag TAG
  38     TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest, EMACS_XX_YY for a
  39     release.
  40
  41 10. admin/make-announcement OLD NEW
  42     This creates an announcement for pretests.  OLD is the version used
  43     to make deltas with respect to NEW.  Anouncements for pretests need
  44     to be crafted by hand.  Use an older announcement to start with.
  45
  46 11. For a pretest, do:
  47     rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta compile-NEW.log \
  48     emacs-NEW.announce alpha.gnu.org:/home/alpha/gnu/emacs/pretest/.
  49     For a release, do:
  50     rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta \
  51     alpha.gnu.org:/home/ftp/gnu/emacs/.
  52
  53 12. Verify that the files are visible at
  54     ftp://alpha.gnu.org/gnu/emacs/pretest/ for a pretest, at
  55     ftp://ftp.gnu.org/gnu/emacs/ for a release.
  56
  57 13. For a pretest, let Richard Stallman know about the new pretest and
  58     tell him to announce it using the announcement you prepared.  Remind
  59     him to set a Reply-to header to <emacs-pretest-bug@gnu.org>.
  60     For a release, Richard should prepare the announcement himself,
  61     possibly starting from a previous announcment.