Mercurial > hg > xemacs-beta

comparison etc/BETA @ 108:360340f9fd5f r20-1b6

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-1b6
author cvs
date Mon, 13 Aug 2007 09:18:39 +0200
parents ec9a17fef872
children e04119814345
comparison
equal deleted inserted replaced
107:523141596bda 108:360340f9fd5f
1 -*- mode:outline; minor-mode:outl-mouse -*-
2
3 * Introduction
4 ==============
5
6 You are running an experimental version of XEmacs. Please do not
7 report problems with Beta XEmacs to comp.emacs.xemacs. Report them to
8 xemacs-beta@xemacs.org.
9
10 ** XEmacs Beta Mailing List
11 ===========================
12
13 *** Subscribing
14 ---------------
15
16 If you are not subscribed to the XEmacs beta list you should be. Send
17 an email message with a subject of `subscribe' (without the quotes) to
18 xemacs-beta-request@xemacs.org and follow the directions. You do not
19 have to fill out the survey if you don't want to.
20
21 *** Unsubscribing
22 -----------------
23
24 To unsubscribe from the list send an email message with a subject of
25 `unsubscribe' (without the quotes) to xemacs-beta-request@xemacs.org.
26
27 *** Administrivia
28 -----------------
29
30 The XEmacs beta list is managed by the SmartList mailing list package,
31 and the usual SmartList commands work. Do not send mailing list
32 requests to the main address (xemacs-beta@xemacs.org), always send
33 them to xemacs-beta-request@xemacs.org. If you have problems with the
34 list itself, they should be brought to the attention of the Mailing
35 List manager Chuck Thompson <cthomp@xemacs.org>.
36
37
38 ** Reporting Problems
39 =====================
40
41 The best way to get problems fixed in XEmacs is to submit good problem
42 reports. Since this is beta software problems are certain to exist.
43 Please read through all of part II of the XEmacs FAQ for an overview
44 of problem reporting. Other items which are most important are:
45
46 1. Do not submit C stack backtraces without line numbers. Since it
47 is possible to compile optimized with debug information with GCC
48 it is never a good idea to compile XEmacs without the -g flag.
49 XEmacs runs on a variety of platforms, and often it is not
50 possible to recreate problems which afflict a specific platform.
51 The line numbers in the C stack backtrace help isolate where the
52 problem is actually occurring.
53
54 2. Attempt to recreate the problem starting with an invocation of
55 XEmacs with `xemacs -q -no-site-file'. Quite often problems are
56 due to package interdependencies, and the like. An actual bug in
57 XEmacs should be reproducible in a default configuration without
58 loading any special packages (or the one or two specific packages
59 that cause the bug to appear).
60
61 3. A picture can be worth a thousand words. When reporting an
62 unusual display, it is generally best to capture the problem in a
63 screen dump and include that with the problem report. The easiest
64 way to get a screen dump is to use the xv program and its grab
65 function. Save the image as a GIF to keep bandwidth requirements
66 down without loss of information. MIME is the preferred method
67 for making the image attachments.
68
69 * Compiling Beta XEmacs
70 =======================
71
72 ** Building an XEmacs from patches
73 ==================================
74
75 All beta releases of XEmacs are included with patches from the
76 previous version in an attempt to keep bandwidth requirements down.
77 Patches should be applied with the GNU patch program in something like
78 the following. Let's say you're upgrading XEmacs 20.4-beta10 to
79 XEmacs 20.4-beta11 and you have a full unmodified XEmacs 20.4-beta10
80 source tree to work with. Cd to the top level directory and issue the
81 shell command:
82
83 $ gunzip -c /tmp/xemacs-20.4-b10-20.4-b11.patch.gz | patch -p1
84
85 After patching check to see that no patches were missed by doing
86 $ find . -name \*.rej -print
87
88 Any rejections should be treated as serious problems to be resolved
89 before starting compilation.
90
91 After seeing that there were no rejections, issue the command
92
93 $ make all-elc
94
95 and go play minesweep for awhile on an older XEmacs while the binary
96 is rebuilt.
97
98 ** Building an XEmacs from a full distribution
99 ==============================================
100
101 Locate a convenient place where you have at least 100MB of free space
102 and issue the command
103
104 $ gunzip -c /tmp/xemacs-20.4-b11.tar.gz | tar xvf -
105
106 (or the simpler `tar zxvf /tmp/xemacs-20.4-b11.tar.gz' if you use GNU
107 tar).
108
109 cd to the top level directory and issue an appropriate configure
110 command. The maintainer uses the following at the time of this
111 writing:
112
113 ./configure --with-offix --with-mule=yes --with-dialogs=athena3d \
114 --cflags="-m486 -g -O4 -fno-strength-reduce -malign-loops=2 \
115 -malign-jumps=2 -malign-functions=2" --with-sound=no \
116 --with-xface=yes --error-checking=all --debug=yes \
117 --with-scrollbars=athena3d \
118 --with-canna=yes --with-wnn=yes --wnn-includes=/usr/X11R6/include/wnn
119
120 Save the output from configure that looks something like:
121 Configured for `i586-unknown-linux2.0.28'.
122
123 Where should the build process find the source code? /usr/src/xemacs-20.0
124 What installation prefix should install use? /usr/local
125 What operating system and machine description files should XEmacs use?
126 `s/linux.h' and `m/intel386.h'
127 What compiler should XEmacs be built with? gcc -m486 -g -O4 -fno-strength-reduce -malign-loops=2 -malign-jumps=2 -malign-functions=2
128 Should XEmacs use the GNU version of malloc? yes
129 Should XEmacs use the relocating allocator for buffers? yes
130 What window system should XEmacs use? x11
131 Where do we find X Windows header files? /usr/X11R6/include
132 Where do we find X Windows libraries? /usr/X11R6/lib
133 Compiling in support for XAUTH.
134 Compiling in support for XPM.
135 Compiling in support for X-Face headers.
136 Compiling in support for GIF image conversion.
137 Compiling in support for JPEG image conversion.
138 Compiling in support for PNG image conversion.
139 Compiling in support for Berkeley DB.
140 Compiling in support for GNU DBM.
141 Compiling in Mule (multi-lingual) support.
142 Compiling in support for OffiX.
143 Using the Lucid menubar.
144 Using the Athena-3d scrollbar.
145 Using the Athena-3d dialog boxes.
146
147 Then type make and you should have a working XEmacs.
148
149 After you have verified that you have a functional editor, fire up
150 your favorite mail program and send a build report to
151 xemacs-beta@xemacs.org. The build report should include
152
153 1. Your hardware configuration (OS version, etc.)
154
155 2. Version numbers of software in use (X11 version, system library
156 versions if appropriate, graphics library versions if appropriate).
157 If you're on a system like Linux, include all the version numbers
158 you can because chances are it makes a difference.
159
160 3. The options given to configure
161
162 4. The configuration report illustrated above
163
164 5. Any other unusual items you feel should be brought to the attention
165 of the developers.