[Success] XEmacs 21.5-b28 "fuki" (+CVS-20071205) powerpc-apple-darwin8.11.0

Stephen J. Turnbull stephen at xemacs.org
Fri Feb 1 18:31:24 EST 2008


This has Jerry's patch to remove a redundant SET_EVENT_MAGIC_X_EVENT
in it.

> XEmacs Build Report generated by emacs-version
> 21.5  (beta28) "fuki" (+Hg: 930bb9cba65a default) XEmacs Lucid
> with system-configuration
> powerpc-apple-darwin8.11.0
> follows:

> Contents of /Users/steve/Software/XEmacs/alioth/xemacs/+build/Installation:
> (Output from most recent run of ./configure)

uname -a: Darwin chibi.local 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh powerpc

../configure  '--with-site-prefixes=/opt/local:/usr/local/canna' '--with-debug' '--with-error-checking=all' '--with-athena=3d' '--with-widgets=athena' '--with-dialogs=athena' '--with-xft=emacs,menubars,tabs,gauges' '--with-bignum=gmp' '--with-memory-usage-stats' '--with-mule' '--with-union-type' '--with-system-packages=/usr/local/lib/xemacs'


XEmacs 21.5-b28 "fuki" (+Hg: 930bb9cba65a default) configured for `powerpc-apple-darwin8.11.0'.

Compilation Environment and Installation Defaults:
  Source code location:              /Users/steve/Software/XEmacs/alioth/xemacs
  Installation prefix:               /usr/local
  Additional prefixes:               /opt/local /usr/local/canna
  Operating system description file: `s/darwin.h'
  Machine description file:          `m/powerpc.h'
  Compiler version:                  powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5370)
    - GCC specs file:                specs.
    - Compiler command:              gcc   -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wunused-parameter -g  
  libc version:                      
  Relocating allocator for buffers:  no
  GNU version of malloc:             no
    - The GNU allocators don't work with this system configuration.

Window System:
  Compiling in support for the X window system:
    - X Windows headers location:                 /usr/X11R6/include
    - X Windows libraries location:               /usr/X11R6/lib
    - Handling WM_COMMAND properly.
    - Using fontconfig to manage fonts.
    - Compiling in support for Xft antialiased fonts (EXPERIMENTAL).
  Compiling in support for the Athena widget set:
    - Athena headers location:                    X11/Xaw3d
    - Athena library to link:                     Xaw3d
  Using Lucid menubars.
    - Using Xft to render antialiased fonts in menubars.
      WARNING: This feature will be replaced with a face.
  Using Lucid scrollbars.
  Using Athena dialog boxes.
  Using Athena native widgets.
    - Using Xft to render antialiased fonts in tab controls.
      WARNING: This feature will be replaced with a face.
    - Using Xft to render antialiased fonts in progress bars.
      WARNING: This feature will be replaced with a face.
      WARNING: This feature not yet implemented; setting ignored.

TTY:
  Compiling in support for ncurses.

Images:
  Compiling in support for GIF  images (builtin).
  Compiling in support for XPM  images.
  Compiling in support for PNG  images.
  Compiling in support for JPEG images.
  Compiling in support for TIFF images.

Sound:

Databases:
  Compiling in support for Berkeley database.
  Compiling in support for GNU DBM.
  Compiling in support for LDAP.

Internationalization:
  Compiling in support for Mule (multi-lingual Emacs).
  Compiling in support for XIM (X11R5+ I18N input method).
    - Using raw Xlib to provide XIM support.
  Compiling in support for Canna on Mule.

Mail:
  Compiling in support for "file" mail spool file locking method.

Other Features:
  Inhibiting IPv6 canonicalization at startup.
  Compiling in support for dynamic shared object modules.
  Compiling in support for more number types using the GNU MP library.
  Using the union type for Lisp_Objects.
  WARNING: ---------------------------------------------------------
  WARNING: This tends to trigger compiler bugs, especially when
  WARNING: combined with MULE and ERROR_CHECKING.  Crashes have
  WARNING: been seen with various versions of GCC (up to about 2.95),
  WARNING: and recently with Visual C++ as well (mid-2003).
  WARNING: More recent versions may be safer, or not.
  WARNING: ---------------------------------------------------------
  Using the new GC mark algorithms (KKCC).
  WARNING: ---------------------------------------------------------
  WARNING: The new algorithms are experimental. They are enabled by
  WARNING: default for this release. Use `--disable-kkcc' to
  WARNING: turn it off.
  WARNING: ---------------------------------------------------------
  Using the new portable dumper.
  Dumping into executable.
  Compiling in support for extra debugging code.
  Compiling in support for runtime error checking.
  WARNING: ---------------------------------------------------------
  WARNING: XEmacs will run noticeably more slowly as a result.
  WARNING: Error checking is on by default for XEmacs beta releases.
  WARNING: ---------------------------------------------------------


> Contents of /Users/steve/Software/XEmacs/alioth/xemacs/+build/beta.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^  \*\* \|^\(FAIL\|SKIP\):"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:\|^\s-*0 .*\(failure\|error\)s?\|^PASS:\|(100%) tests successful"

running CONFIG_SHELL=/bin/sh /bin/sh ../configure  --with-site-prefixes=/opt/local:/usr/local/canna --with-debug --with-error-checking=all --with-athena=3d --with-widgets=athena --with-dialogs=athena --with-xft=emacs,menubars,tabs,gauges --with-bignum=gmp --with-memory-usage-stats --with-mule --with-union-type --with-system-packages=/usr/local/lib/xemacs  --no-create --no-recursion
checking for preferred warning flags for XEMACS_CC... -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wunused-parameter
checking for preferred warning flags for CC... -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wdeclaration-after-statement -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes
checking for dlerror... yes
checking for _dlerror... no
checking for ldap_result2error... yes
checking for strerror in -lintl... yes
checking for perror... yes
checking for strerror... yes
Compilation Environment and Installation Defaults:
  Compiling in support for runtime error checking.
make  all
cd ./lib-src && make  all
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.c:950: warning: no previous prototype for 'getopt'
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regcomp
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regexec
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regfree
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regcomp
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regexec
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regfree
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regcomp
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regexec
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regfree
/Users/steve/Software/XEmacs/alioth/xemacs/lib-src/getopt.h:107: warning: function declaration isn't a prototype
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regcomp
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regexec
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple definitions of symbol _regfree
cd ./lwlib && make  all
cd ./src && make  all
/Users/steve/Software/XEmacs/alioth/xemacs/src/objects-xlike-inc.c:435: warning: pointer targets in initialization differ in signedness
/Users/steve/Software/XEmacs/alioth/xemacs/src/objects-xlike-inc.c:439: warning: pointer targets in initialization differ in signedness
/Users/steve/Software/XEmacs/alioth/xemacs/src/objects-xlike-inc.c:441: warning: pointer targets in initialization differ in signedness
/Users/steve/Software/XEmacs/alioth/xemacs/src/objects-xlike-inc.c:445: warning: pointer targets in initialization differ in signedness
/Users/steve/Software/XEmacs/alioth/xemacs/src/objects-xlike-inc.c:521: warning: pointer targets in initialization differ in signedness
Using load-path (/Users/steve/Software/XEmacs/alioth/xemacs/lisp/)
Using module-load-path (/Users/steve/Software/XEmacs/alioth/xemacs/+build/modules)
Generating autoloads for lisp/next-error.el...
While compiling the end of the data in file /Users/steve/Software/XEmacs/alioth/xemacs/lisp/menubar-items.el:
  ** the function bookmark-all-names is not known to be defined.
While compiling make-8-bit-generate-helper in file /Users/steve/Software/XEmacs/alioth/xemacs/lisp/mule/mule-coding.el:
  ** variable args-out-of-range bound but not referenced
Using load-path (/Users/steve/Software/XEmacs/alioth/xemacs/lisp/)
Using module-load-path (/Users/steve/Software/XEmacs/alioth/xemacs/+build/modules)
Using load-path (/Users/steve/Software/XEmacs/alioth/xemacs/lisp/)
Using module-load-path (/Users/steve/Software/XEmacs/alioth/xemacs/+build/modules)
Using load-path (/Users/steve/Software/XEmacs/alioth/xemacs/lisp/)
Using module-load-path (/Users/steve/Software/XEmacs/alioth/xemacs/+build/modules)
Requiring next-error...
Compiling /Users/steve/Software/XEmacs/alioth/xemacs/lisp/next-error.el...
Wrote /Users/steve/Software/XEmacs/alioth/xemacs/lisp/next-error.elc
While compiling fc-pattern-p in file /Users/steve/Software/XEmacs/alioth/xemacs/lisp/font-mgr.el:
  ** subr fc-pattern-p being redefined as a function
While compiling fc-pattern-create:
  ** subr fc-pattern-create being redefined as a function
While compiling fc-name-parse:
  ** subr fc-name-parse being redefined as a function
While compiling fc-name-unparse:
  ** subr fc-name-unparse being redefined as a function
While compiling fc-pattern-duplicate:
  ** subr fc-pattern-duplicate being redefined as a function
While compiling fc-pattern-add:
  ** subr fc-pattern-add being redefined as a function
While compiling fc-pattern-del:
  ** subr fc-pattern-del being redefined as a function
While compiling fc-pattern-get:
  ** subr fc-pattern-get being redefined as a function
While compiling fc-font-match:
  ** subr fc-font-match being redefined as a function
While compiling fc-list-fonts-pattern-objects:
  ** subr fc-list-fonts-pattern-objects being redefined as a function
While compiling fc-font-sort:
  ** subr fc-font-sort being redefined as a function
While compiling xlfd-font-name-p:
  ** subr xlfd-font-name-p being redefined as a function
While compiling ethio-modify-vowel in file /Users/steve/Software/XEmacs/alioth/xemacs/lisp/mule/ethio-util.el:
  ** decompose-composite-char is an obsolete function; use char-to-string instead.
While compiling cyrillic-encode-koi8-r-char in file /Users/steve/Software/XEmacs/alioth/xemacs/lisp/mule/cyril-util.el:
  ** reference to free variable cyrillic-koi8-r-to-external-code-table
While compiling cyrillic-encode-alternativnyj-char:
  ** reference to free variable cyrillic-alternativnyj-to-external-code-table
Computing custom-loads for next-error...
cd ./modules/ldap && make  all
cd ./modules/canna && make  all
/Users/steve/Software/XEmacs/alioth/xemacs/modules/canna/canna_api.c:730: warning: pointer targets in passing argument 2 of 'RkBgnBun' differ in signedness
cd /Users/steve/Software/XEmacs/alioth/xemacs/man && make  info
cd ./lib-src && make  all
cd ./lwlib && make  all
cd ./src && make  all
cd ./modules/ldap && make  all
cd ./modules/canna && make  all
cd /Users/steve/Software/XEmacs/alioth/xemacs/man && make  info
cd ./src && make  check
base64-tests.el:         1234 of  1234 tests successful (100%).
byte-compiler-tests.el:   104 of   104 tests successful (100%).
c-tests.el:                 4 of     4 tests successful (100%).
case-tests.el:           1168 of  1168 tests successful (100%).
ccl-tests.el:            4570 of  4570 tests successful (100%).
database-tests.el:         20 of    20 tests successful (100%).
extent-tests.el:          194 of   194 tests successful (100%).
hash-table-tests.el:     9868 of  9868 tests successful (100%).
iso-ir-196-test.el:         2 of     2 tests successful (100%).
lisp-reader-tests.el:      52 of    52 tests successful (100%).
lisp-tests.el:           3772 of  3772 tests successful (100%).
md5-tests.el:              56 of    56 tests successful (100%).
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
KNOWN BUG: (loop for i from 0 to 1114111 with exceptions = #<range-table [55296 57343] t [64976 65007] t [65534 65535] t 0x515f22> do (unless (get-range-table i exceptions) (read (format (if (> i 65535) "?\\U%08X" "?\\u%04X") i))) finally return t) ==> error invalid-constant, as expected
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
KNOWN BUG: (loop for i from 0 to 1114111 with exceptions = #<range-table [55296 57343] t [64976 65007] t [65534 65535] t 0x862b16> do (unless (get-range-table i exceptions) (read (format (if (> i 65535) "?\\U%08X" "?\\u%04X") i))) finally return t) ==> error invalid-constant, as expected
mule-tests.el:           1082 of  1098 tests successful ( 98%).
    12 tests skipped because input method unavailable.
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-5-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
KNOWN BUG: (loop for i from 0 to 1114111 with exceptions = #<range-table [55296 57343] t [64976 65007] t [65534 65535] t 0x515f22> do (unless (get-range-table i exceptions) (read (format (if (> i 65535) "?\\U%08X" "?\\u%04X") i))) finally return t) ==> error invalid-constant, as expected
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-5-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
FAIL: Assertion failed: (assoc language-input-method input-method-alist)
SKIP: "check that IM latin-4-prefix can be activated" BECAUSE "input method unavailable"
KNOWN BUG: (loop for i from 0 to 1114111 with exceptions = #<range-table [55296 57343] t [64976 65007] t [65534 65535] t 0x862b16> do (unless (get-range-table i exceptions) (read (format (if (> i 65535) "?\\U%08X" "?\\u%04X") i))) finally return t) ==> error invalid-constant, as expected
	    2 errors that should have been generated, but weren't
os-tests.el:               10 of    10 tests successful (100%).
    2 tests skipped because tac executable not found.
SKIP: "Tests of call-process-region with region deleted after inserting
tac process output." BECAUSE "tac executable not found"
SKIP: "Tests of call-process-region with region deleted after inserting
tac process output." BECAUSE "tac executable not found"
regexp-tests.el:          372 of   372 tests successful (100%).
region-tests.el:           28 of    28 tests successful (100%).
symbol-tests.el:          252 of   252 tests successful (100%).
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
syntax-tests.el:           84 of    90 tests successful ( 93%).
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
tag-tests.el:               6 of     6 tests successful (100%).
weak-tests.el:            140 of   140 tests successful (100%).
base64-tests.el:         1234 of  1234 tests successful (100%).
byte-compiler-tests.el:   104 of   104 tests successful (100%).
c-tests.el:                 4 of     4 tests successful (100%).
case-tests.el:           1168 of  1168 tests successful (100%).
ccl-tests.el:            4570 of  4570 tests successful (100%).
database-tests.el:         20 of    20 tests successful (100%).
extent-tests.el:          194 of   194 tests successful (100%).
hash-table-tests.el:     9868 of  9868 tests successful (100%).
iso-ir-196-test.el:         2 of     2 tests successful (100%).
lisp-reader-tests.el:      52 of    52 tests successful (100%).
lisp-tests.el:           3772 of  3772 tests successful (100%).
md5-tests.el:              56 of    56 tests successful (100%).
mule-tests.el:           1082 of  1098 tests successful ( 98%).
os-tests.el:               10 of    10 tests successful (100%).
regexp-tests.el:          372 of   372 tests successful (100%).
region-tests.el:           28 of    28 tests successful (100%).
symbol-tests.el:          252 of   252 tests successful (100%).
syntax-tests.el:           84 of    90 tests successful ( 93%).
tag-tests.el:               6 of     6 tests successful (100%).
weak-tests.el:            140 of   140 tests successful (100%).

/Users/steve/Software/XEmacs/alioth/xemacs/+build/xemacs-make-install.err not found!

/Users/steve/Software/XEmacs/alioth/xemacs/+build/xemacs-make-check.err not found!

/Users/steve/Software/XEmacs/alioth/xemacs/+build/xemacs-make-check-temacs.err not found!

/Users/steve/Software/XEmacs/alioth/xemacs/+build/xemacs-make-all.err not found!


--86B8818945D9.1201908692/chibi.local--

>From MAILER-DAEMON  Fri Feb  1 22:18:31 2008
Return-Path: <>
X-Original-To: steve at chibi.local
Delivered-To: steve at chibi.local
Received: by chibi.local (Postfix)
	id 29274189CF23; Fri,  1 Feb 2008 22:18:31 -0800 (PST)
Date: Fri,  1 Feb 2008 22:18:31 -0800 (PST)
From: MAILER-DAEMON at chibi.local (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: steve at chibi.local
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="22BFE189CF1E.1201933111/chibi.local"
Message-Id: <20080202061831.29274189CF23 at chibi.local>
Status: RO

This is a MIME-encapsulated message.

--22BFE189CF1E.1201933111/chibi.local
Content-Description: Notification
Content-Type: text/plain

This is the Postfix program at host chibi.local.

I'm sorry to have to inform you that your message could not be
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

			The Postfix program

<xemacs-patches at xemacs.org>: host mail.xemacs.org[207.172.156.133] said: 553
    5.1.8 <steve at chibi.local>... Domain of sender address steve at chibi.local
    does not exist (in reply to MAIL FROM command)

--22BFE189CF1E.1201933111/chibi.local
Content-Description: Delivery report
Content-Type: message/delivery-status

Reporting-MTA: dns; chibi.local
X-Postfix-Queue-ID: 22BFE189CF1E
X-Postfix-Sender: rfc822; steve at chibi.local
Arrival-Date: Fri,  1 Feb 2008 22:18:23 -0800 (PST)

Final-Recipient: rfc822; xemacs-patches at xemacs.org
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mail.xemacs.org[207.172.156.133] said: 553
    5.1.8 <steve at chibi.local>... Domain of sender address steve at chibi.local
    does not exist (in reply to MAIL FROM command)

--22BFE189CF1E.1201933111/chibi.local
Content-Description: Undelivered Message
Content-Type: message/rfc822

Received: by chibi.local (Postfix, from userid 501)
	id 22BFE189CF1E; Fri,  1 Feb 2008 22:18:23 -0800 (PST)
From: "Stephen J. Turnbull" <stephen at xemacs.org>
To: XEmacs Patches <xemacs-patches at xemacs.org>
Subject: [AC web] Update *access.html to December 2007 realities
Message-Id: <20080202061823.22BFE189CF1E at chibi.local>
Date: Fri,  1 Feb 2008 22:18:23 -0800 (PST)

APPROVE COMMIT web

Doc patch, let me know if I messed anything up.  Thanks to Joachim
Schrod for pointing out the need.

Index: Develop/ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/ChangeLog,v
retrieving revision 1.105
diff -u -U0 -r1.105 ChangeLog
--- Develop/ChangeLog	24 Mar 2007 15:30:19 -0000	1.105
+++ Develop/ChangeLog	2 Feb 2008 06:10:03 -0000
@@ -0,0 +1,9 @@
+2008-02-01  Stephen J. Turnbull  <stephen at xemacs.org>
+
+	* hgaccess.content: New file based on cvsaccess.html.
+
+	* index.content: Add reference to hgaccess.html.
+	Add reference to beta.html.
+
+	* cvsaccess.content: Add reference to hgaccess.html.
+

Index: Develop/index.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/index.content,v
retrieving revision 1.15
diff -u -r1.15 index.content
--- Develop/index.content	8 Nov 2003 22:37:13 -0000	1.15
+++ Develop/index.content	2 Feb 2008 06:15:55 -0000
@@ -8,20 +8,39 @@
 
   <h2 id="xemacs">XEmacs Development</h2>
 
+  <p>As of 5 December 2007, the development mainline (aka version
+    21.5) has been moved to a
+    <a href="http://hgbook.red-bean.com/hgbook.html">Mercurial</a>
+    repository on <code>hg.debian.org</code> from which you may
+    <a href="http://hg.debian.org/hg/xemacs/xemacs">browse</a> the
+    latest checked-in code.  Please see the introduction to the
+    <a href="hgaccess.html">XEmacs Mercurial Repository</a> for
+    instructions on its use.</p>
+
+  <p>Other XEmacs repositories, including the 21.4 branch, the
+    packages, and the sources for this website, continue to be
+    provided by the CVS repository on <code>cvs.xemacs.org</code>,
+    hosted by our friends at <code>dotsrc.org</code>.</p>
+
   <p>
-    More detailed information is forthcoming, but in the short term,
-    if you'd like to help with the XEmacs development effort, do the
+    If you'd like to help with the XEmacs development effort, do the
     following:</p>
 
   <ol>
     <li>
       <p>
-        <a href="../Download/index.html">Download</a> the
-        latest beta release, or (better) go to <a href="<!-- _GP_
-        relPath(qq{Develop/cvsaccess.html}) -->"><!--
-        _GP_ relPath(qq{Develop/cvsaccess.html}) --></a> and follow
-        the instructions to get an up-to-date CVS tree of the XEmacs
-        source.</p>
+        <a href="<!-- _GP_ relPath(qq{Download/index.html}) -->">Download</a>
+	the latest releases of 21.4 (the stable branch) or 21.5 (the
+	development mainline, or (better) get the most up-to-date
+	sources from the source repositories.  For 21.5, see the
+	introduction to the
+	<a href="hgaccess.html">XEmacs Mercurial Repository</a> and
+	follow the instructions to get an up-to-date tree of the
+	XEmacs 21.5 source.  For other resources, such as the 21.4
+	stable tree, the package tree and the source to this website,
+	see the introduction to the
+	<a href="cvsaccess.html">XEmacs CVS Repository</a> and follow
+	the instructions to get an up-to-date trees of those resources.</p>
     </li>
     <li>
       <p>
@@ -51,8 +70,12 @@
 
       <p>
         The rules for creating and submitting patches are set forth in
-        etc/BETA (look for <strong>Creating patches for submission</strong>
-        in documentation accessed via M-x <strong>describe-beta</strong>)</p>
+        etc/BETA (section <strong>Creating patches for submission</strong>
+	in documentation accessed via M-x <strong>describe-beta</strong>),
+	or see the
+	<a href="<!-- _GP_ relPath(qq{Documentation/21.5/html/beta.html}) -->">
+	  web version</a>.
+      </p>
 
       <p>
         You may find the <a
Index: Develop/cvsaccess.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Develop/cvsaccess.content,v
retrieving revision 1.30
diff -u -r1.30 cvsaccess.content
--- Develop/cvsaccess.content	12 Jan 2006 09:41:58 -0000	1.30
+++ Develop/cvsaccess.content	2 Feb 2008 06:15:55 -0000
@@ -9,8 +9,22 @@
 
   <h1>XEmacs CVS Repository</h1>
 
-  <p>
-    Please review the information below even if you are familiar with
+  <p>As of 5 December 2007, the development mainline (aka version
+    21.5) has been moved to a
+    <a href="http://hgbook.red-bean.com/hgbook.html">Mercurial</a>
+    repository on <code>hg.debian.org</code> from which you may
+    <a href="http://hg.debian.org/hg/xemacs/xemacs">browse</a> the
+    latest checked-in code.  Please see the introduction to the
+    <a href="hgaccess.html">XEmacs Mercurial Repository</a> for
+    instructions on its use.</p>
+
+  <p>Other XEmacs repositories, including the 21.4 branch, the
+    packages, and the sources for this website, continue to be
+    provided by the CVS repository on <code>cvs.xemacs.org</code>,
+    hosted by our friends at <code>dotsrc.org</code>.  This page
+    describes access to those resources.</p>
+
+  <p>Please review the information below even if you are familiar with
     the XEmacs CVS repository.</p>
 
   <ul>
Index: Develop/hgaccess.content
===================================================================
RCS file: Develop/hgaccess.content
diff -N Develop/hgaccess.content
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ Develop/hgaccess.content	2 Feb 2008 06:15:55 -0000
@@ -0,0 +1,455 @@
+%title%
+XEmacs CVS Archive
+%author%
+Jareth Hein &lt;jareth at xemacs.org&gt;
+Steve Youngs &lt;youngs at xemacs.org&gt;
+Adrian Aichner &lt;adrian at xemacs.org&gt;
+Stephen J. Turnbull &lt;stephen at xemacs.org&gt;
+%main%
+
+    <h1>XEmacs Mercurial Repository</h1>
+
+    <p>As of 5 December 2007, the development mainline (aka version
+      21.5) has been moved to a
+      <a href="http://hgbook.red-bean.com/hgbook.html">Mercurial</a>
+      repository on <code>hg.debian.org</code> from which you may
+      <a href="http://hg.debian.org/hg/xemacs/xemacs">browse</a> the
+      latest checked-in code.  This page describes access to those
+      resources.</p>
+
+    <p>Other XEmacs repositories, including the 21.4 branch, the
+      packages, and the sources for this website, continue to be
+      provided by the CVS repository on <code>cvs.xemacs.org</code>,
+      hosted by our friends at <code>dotsrc.org</code>.  Please see the
+      introduction to the <a href="cvsaccess.html">XEmacs CVS
+	Repository</a> for instructions on its use.</p>
+
+    <p><strong>Please note:</strong> This page was hacked up quickly
+      by copying and editing the corresponding page for CVS.  If you
+      spot any CVS-isms or other statements that are not correct for
+      the new repository, please report it as a bug to the
+      <a href="mailto:xemacs-beta at xemacs.org">XEmacs Developers</a>.</p>
+
+    <ul>
+
+      <li><a href="#quickstart">Quick start guide</a></li>
+
+      <li><a href="#whatishg">What is Mercurial?</a></li>
+
+      <li><a href="#tutorial">Using the XEmacs Mercurial server</a></li>
+
+      <li><a href="#tags">Tags: what they are and their use</a></li>
+
+      <li><a href="#packages">Packages info</a></li>
+
+      <li><a href="#webaccess">Web access to the trees</a></li>
+
+      <li><a href="#committers">Commit (R/W) access to the CVS trees</a></li>
+
+      <li><a href="#recent">Recent news</a></li>
+
+    </ul>
+
+    <p>
+      This site has a collection of
+      <a href="http://www.selenic.com/">Mercurial</a>trees for XEmacs,
+      a feature-packed text-editing environment based on Lisp.  For
+      general information about XEmacs, check out the
+      <a href="http://www.xemacs.org">XEmacs main WWW server</a>.</p>
+
+    <h3><a name="quickstart">Quick Start Guide</a></h3>
+
+    <p>
+      To get the official (21.5) development sources, do:
+    <pre xml:space="preserve">
+      <strong>hg clone http://hg.debian.org/hg/xemacs/xemacs-beta</strong>
+    </pre>
+    To get the bleeding edge patches that are still under review (and
+    in some cases may already have been vetoed or be known to cause
+    crashes and other showstoppers) do:
+    <pre xml:space="preserve">
+      <strong>hg clone http://hg.debian.org/hg/xemacs/xemacs</strong>
+    </pre>
+    instead.  The XEmacs lisp packages are now unbundled, and are
+    available from the <a href="cvsaccess.html">CVS repository</a>.
+    Older versions of XEmacs, including the currently stable version
+    (21.4) may also be checked out from <a href="cvsaccess.html">CVS
+      repository</a>.</p>
+
+    <p>
+      Each of these components are available separately as non-CVS
+      tarballs via HTTP and FTP.  Here are the current HTTP URLs:</p>
+     <ul>
+      <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.5"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.5</strong></a></li>
+      <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.4"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.4</strong></a></li>
+      <li><a href="http://ftp.xemacs.org/pub/xemacs/xemacs-21.1"><strong>http://ftp.xemacs.org/pub/xemacs/xemacs-21.1</strong></a></li>
+      <li><a href="http://ftp.xemacs.org/pub/xemacs/packages"><strong>http://ftp.xemacs.org/pub/xemacs/packages</strong></a></li>
+    </ul>
+    <p>If you prefer FTP for some reason, simply change the URL scheme
+      from "http" to "ftp".</p>
+
+    <hr />
+    <h3><a name="whatishg">What is Mercurial?</a></h3>
+
+    <p>
+      <a href="http://hgbook.red-bean.com/hgbook.html">Mercurial</a>
+      is a modern version control system (VCS) that not only keeps
+      track of older versions also handles branching and distributed
+      development well.  Unlike CVS or Subversion (the defacto
+      industry-standard source code control system for open source
+      software projects), every Mercurial checkout is a full
+      repository, containing all of the project's history.  Because
+      the archives are compressed, a full repository (back to 21.5.0)
+      requires much less than twice the space of the source tree
+      alone.  Unlike many other VCSes (including CVS and git)
+      Mercurial is perfectly happy to serve remote clients over an
+      ordinary HTTP connection, using an unmodified httpd and a tiny
+      CGI.  This means that you can easily share your
+      version-controlled patches with others, even if they are not
+      accepted for the mainline.
+    </p>
+    <p>
+      Regular contributors to XEmacs are strongly encouraged to get
+      Mercurial write access to the source repository.  This
+      distributes most of the patch-tracking work to those most
+      qualified to do it, namely the patch authors.  XEmacs source
+      code maintenance is basically organized on the bazaar model -
+      we'd like to have as many people as possible, including
+      <strong>you</strong>, making high quality contributions to the
+      source code, in parallel.  But even if you are just a lurker
+      with no desire to make any modifications to the tree, Mercurial
+      gives you a painless way to upgrade between versions.
+    </p>
+
+    <p>
+      By current standards, these trees are moderate in size.  XEmacs
+      21.5 sources will take up 80 MB of hard drive space, before
+      compilation, the Mercurial metadata and archive about as much.
+      A typical build will add about 60 MB of build products, for a
+      total of about 220 MB required for core development.  Add in
+      the lisp packages tree (another 120 MB of source, with compiled
+      Lisp taking about 70MB) in your calculations if you're
+      interested in messing with them too.
+      <!-- #### Update these:
+      All in all, the total tree size for the XEmacs core tree is
+      196MB, comprising over 2006 files with 397754-some odd lines of
+      code.  Packages add another 4042 files for 760315 lines of lisp.
+      -->
+    </p>
+
+    <hr />
+    <h3><a name="tutorial">Using the XEmacs Mercurial server</a></h3>
+
+    <p>
+      If you're interested in using the XEmacs Mercurial trees
+      directly, you'll need to install Mercurial.  Mercurial is highly
+      portable because it is entirely written in Python.  Binary
+      packages are available for most platforms, either through native
+      package distributions or from
+      <a href="http://www.selenic.com/mercurial/wiki/index.cgi/Download">
+	Selenic</a>.
+
+    <p>
+      Unlike many centralized servers, XEmacs's Mercurial repository
+      does not require login for cloning the repository.  (Note: for
+      modern distributed VCSes, whole repository is duplicated and can
+      stand alone, so we use the word "clone" rather than "checkout".
+      "Checkout" is used to describe the operation of copying files
+      from the repository archive to the working copy, whether to
+      revert undesirable changes in a single file, or to switch the
+      entire working copy over to another branch.)  The clone
+      operation is simple.
+    </p>
+
+    <p>
+      First cd to the place you want to put the tree, and actually
+      clone the repository.</p>
+
+    <pre xml:space="preserve">
+chibi$ <strong>hg clone http://hg.debian.org/hg/xemacs/xemacs-beta xemacs-21.5</strong>
+<i>(churn, churn, churn)</i>
+    </pre>
+
+    <p>
+      And voila!  One <strong>xemacs-21.5</strong> directory complete
+      with the latest versions of the base code.  Packages are
+      separate, of course.</p>
+
+    <p>
+      The last argument <code>xemacs-21.5</code> gives the name of the
+      directory to use as a workspace.  The repository metadata and
+      archives go in the <code>.hg</code> subdirectory, and there will
+      usually be a <code>.hgignore</code> file containing regexps
+      matching names of files to ignore for version control purposes.
+      If the tree root name (here <code>xemacs-21.5</code>) is
+      omitted, it will be defaulted to the basename of the URL being
+      cloned.</p>
+
+    <p>
+      You probably want to create a <code>~/.hgrc</code> file to
+      configure your local defaults.  At least it's worth setting your
+      Mercurial username:</p>
+
+    <pre xml:space="preserve"><tt>
+[ui]
+username = J. Random Hacker &lt;jrhacker at example.com&gt;
+    </tt></pre>
+
+    <p>
+      so that any local commits to your own repository look nice.
+      (Feel free to commit what you like, it's <em>your</em>
+      repository.  If you expect to contribute upstream, however, you
+      may want to keep a separate "pristine" workspace or learn about
+      named branches.)</p>
+
+    <p>
+      When there is an upstream update, you can get the whole skinny
+      quick, fast and relatively painlessly with the following command
+      (executed from the directory created by <tt><strong>hg
+	  clone</strong></tt>).</p>
+
+    <pre xml:space="preserve">
+chibi$ <strong>hg pull -u</strong>
+    </pre>
+
+    <p>
+      The <code>-u</code> switch automatically updates your workspace
+      to correspond to the tip.</p>
+
+    <h3><a name="tags">Just how much do you want to bleed?</a></h3>
+
+    <p>
+      XEmacs developers push their commits on an asynchronous basis.
+      The idea is to keep those actively coding on the same page by
+      making everyone's most recent code available in a central place.
+      There is no strong guarantee that the tip of the default
+      Mercurial branch even compiles for anyone.  This means that if
+      you blindly do a <strong>hg pull -u</strong>, there is a good
+      chance that what you get is not functional.</p>
+
+    <p>There are several ways to deal with the churn.</p>
+
+    <ul>
+      <li>Since you have the whole repository available, you can
+	simply revert to an earlier revision.
+	<pre xml:space="preserve">
+chibi$ hg checkout -r 1234
+	</pre>
+	If this mechanism satisfies you, you may even want to clone
+	and update to the completely unfiltered repository that the
+	active developers are committing to:
+	<pre xml:space="preserve">
+chibi$ <strong>hg clone http://hg.debian.org/hg/xemacs/xemacs xemacs-21.5</strong>
+	</pre>
+      </li>
+      <li>
+	You can also take advantage of the review process, and use the
+	<code>xemacs-beta</code> repository as described above.</li>
+      <li>
+	Finally, the most conservative approach is to checkout only
+	the official releases.  These are identical to the tarballs
+	distributed by <code>xemacs.org</code>, and are identified in
+	the <code>xemacs-beta</code> repository by tags of the form
+	<i>rX-Y-Z</i>, corresponding to the version number X.Y.Z (or
+	X.Y-bZ).  X is the major version, Y the minor version, and Z
+	the micro version or patchlevel.</li>
+    </ul>
+
+    <p>
+      In general, tags are admissible anywhere a revision number or
+      hash is allowed.  To checkout a particular revision use the
+      <code>checkout</code> command with the <strong>-r
+      &lt;TAG&gt;</strong> option to. Therefore, to update to 21.5
+      beta 16 (but no further), you'd type:</p>
+
+    <pre xml:space="preserve">
+chibi$ <strong>hg checkout -r r21-5-16</strong>
+    </pre>
+
+    <p>
+      The most recent patchlevel or beta release is identified by the
+      tag <i>rX-Y-latest-beta</i>.</p>
+
+    <p>
+      For more info, check the Mercurial documentation:</p>
+    <ul>
+      <li>the <a href="http://hgbook.red-bean.com/hgbook.html">
+	  Mercurial book</a></li>
+      <li>the <a href="http://www.selenic.com/mercurial/wiki/">
+	  Mercurial wiki</a></li>
+      <li>the builtin help, using <code>hg help</code></li>
+    </ul>
+
+    <hr />
+
+    <h3><a name="packages">New Package system</a></h3>
+
+    <p>
+      For those of you wishing to work with XEmacs 21, you should
+      probably know about our new packaging system. All the details are
+      available <a href="packages.html">here</a>, and there is also an
+      <a href="cvsaccess.html#packages">introduction to the packages
+	CVS repository</a>.</p>
+
+    <h3><a name="webaccess">Web Access</a></h3>
+
+    <p>
+      You can browse the repositories simply by accessing the
+      repositories with any web browser.</p>
+
+    <ul>
+      <li>The <a href="http://hg.debian.org/hg/xemacs/xemacs-beta">
+	  reviewed and approved beta versions</a></li>
+      <li>The <a href="http://hg.debian.org/hg/xemacs/xemacs">raw
+	  patch stream</a></li>
+    </ul>
+
+    <hr />
+    <h3><a name="committers">Commit (R/W) access to the Mercurial tree</a></h3>
+
+    <p>
+      Anybody who has become reasonably well-known to the
+      <a href="jobs.html">XEmacs Reviewers</a> can get access to 
+      commit to the repository.  This has the following advantages:</p>
+
+    <ul>
+
+      <li>
+        The revision history will contain the true author of a change,
+        which makes tracking changes easier, and gives credit where
+        credit is due.</li>
+
+      <li>
+        Committers are more likely to take responsibility for their
+        changes when they are directly modifying the repository
+        themselves.</li>
+
+    </ul>
+
+    <p>
+      To qualify to be a committer, you should have a history of
+      submitting successful patches to
+      <a href="http://list-archive.xemacs.org/xemacs-patches/">
+	xemacs-patches</a></p>
+
+    <p>
+      Currently we are adding new committers using the following
+      method (which may change):</p>
+
+    <ol>
+      <li>
+        Make sure ssh (version 1 or 2) is installed on your
+        computer.</li>
+
+      <li><p>
+	  Get yourself a ssh public key.  Here is some unsolicited
+	  advice on maintaining your ssh key:</p>
+
+	<p>
+	  In general, you should only have ONE identity that you expose
+	  to the outside world.  Create only ONE key pair:
+	  <tt>~/.ssh/identity</tt> and <tt>~/.ssh/identity.pub</tt>
+	  for version 1.  Or for version 2, one of either
+	  <tt>~/.ssh/id_rsa</tt> and <tt>~/.ssh/id_rsa.pub</tt> or
+	  <tt>~/.ssh/id_dsa</tt> and <tt>~/.ssh/id_dsa.pub</tt>
+	  with <tt>ssh-keygen</tt>, and change the comment to something
+	  more meaningful like your email address.  Your ssh public key
+	  is a lot like a business card.</p>
+
+	<p>
+	  For example, I modified the comment in my version 1 public key
+	  using</p>
+
+	<pre xml:space="preserve">
+ssh-keygen -c -C 'Steve Youngs &lt;youngs at xemacs.org&gt;'
+	</pre>
+
+	<p>
+	  SSH version 2 is slightly different.  If you try the above
+	  command on a version 2 key you'll get an error saying that
+	  comments are only supported for version 1 keys.  Don't believe
+	  everything you read, you can have a comment in a version 2
+	  key.  You just have to add the comment when you create the
+	  key:</p>
+
+	<pre xml:space="preserve">
+ssh-keygen -t dsa -C 'Steve Youngs &lt;youngs at xemacs.org&gt;'
+	</pre>
+
+	<p>
+	  After you have created your keys, copy the <tt>~/.ssh/identity</tt>
+	  or <tt>~/.ssh/id_dsa</tt> or <tt>~/.ssh/id_rsa</tt> file to
+	  all the machines you run ssh <strong>from</strong>.</p>
+
+	<p>
+	  Also, append your public key file <tt>~/.ssh/identity.pub</tt>
+	  to the <tt>~/.ssh/authorized_keys</tt> file for SSH 1 or
+	  <tt>~/.ssh/id_(dsa|rsa).pub</tt> to
+	  <tt>~/.ssh/authorized_keys2</tt> on all the machines you run
+	  ssh <strong>to</strong>.</p>
+
+	<p>
+	  When people ask you for your public ssh key, just send them
+	  the contents of <tt>~/.ssh/identity.pub</tt> or
+	  <tt>~/.ssh/id_dsa.pub</tt> or
+	  <tt>~/.ssh/id_rsa.pub</tt>.</p></li>
+
+      <li>
+	If you are not already a Debian developer, you'll need to go
+	to <a href="http://alioth.debian.org/">Alioth</a>
+	(<code>http://alioth.debian.org/</code>) and get an account
+	for guest developers.  If you're not a Debian person, it will
+	have "-guest" appended to it, so be prepared.  (Sorry,
+	"unwelcome-guest" is already taken, but I can think of a few
+	others that are moderately creative.  Think!)</li>
+
+      <li>
+        Send the <a href="mailto:mike at xemacs.org">Mercurial
+	  Administrator</a> your Alioth user name and your public
+        ssh key (i.e. the contents of <tt>~/.ssh/identity.pub</tt> for
+        SSH 1, or <tt>~/.ssh/id_dsa.pub</tt> or
+        <tt>~/.ssh/id_rsa.pub</tt> for SSH 2).  The administrator
+        will take care of the administrivia to give you
+        access.</p></li>
+
+      <li>
+	<p>
+	  Add this stanza to your <tt>~/.ssh/config</tt> file (create it
+	  if necessary):</p>
+
+	<pre xml:space="preserve">
+Host hg.debian.org
+	User		<i>alioth-user</i>-guest
+	ForwardX11	no
+	ForwardAgent	no
+	</pre>
+      </li>
+
+    <hr />
+    <h3><a name="recent"></a>News and changes</h3>
+
+    <h5>2008-02-01</h5>
+
+    <h4>Changes by Stephen:</h4>
+
+    <p>
+      Steal the contents of cvsaccess.html and modify them for
+      Mercurial.</p>
+
+  <!-- Keep this comment at the end of the file
+  Local variables:
+  mode: xml
+  sgml-omittag:nil
+  sgml-shorttag:nil
+  sgml-namecase-general:nil
+  sgml-general-insert-case:lower
+  sgml-minimize-attributes:nil
+  sgml-always-quote-attributes:t
+  sgml-indent-step:2
+  sgml-indent-data:t
+  sgml-parent-document:("../template.html" "html" "body" "table" "tr" "td")
+  sgml-exposed-tags:nil
+  sgml-local-catalogs:nil
+  sgml-local-ecat-files:nil
+  End:
+  -->

--22BFE189CF1E.1201933111/chibi.local--


More information about the XEmacs-Buildreports mailing list