xemacs-beta: man/beta.texi comparison

comparison man/beta.texi @ 3388:e7fb0df1caea

[xemacs-hg @ 2006-05-09 05:15:15 by stephent] Improve beta Info. <87ody7n5k6.fsf@tleepslib.sk.tsukuba.ac.jp>

author	stephent
date	Tue, 09 May 2006 05:15:15 +0000
parents	89e2f8e3f660
children	1094d6d400fb

comparison

equal deleted inserted replaced

-:f5d8dba84d4f
+:e7fb0df1caea
 @author XEmacs Development Team
 @page
 @vskip 0pt plus 1fill
 @noindent
+Copyright @copyright{} 2006 Free Software Foundation. @*
 Copyright @copyright{} 2005 Ben Wing. @*
 This file is part of XEmacs.
 XEmacs is free software; you can redistribute it and/or modify it
 @ifinfo
 @node Top, Introduction, (dir), (dir)
 This Info file describes info relevant to beta versions of XEmacs.
 @menu
 * Introduction::
-* Compiling Beta XEmacs::
+* Building Beta XEmacs::
 * Packages::
+* Reporting Problems::
 * Improving XEmacs::
 * Index::
 @detailmenu
 --- The Detailed Node Listing ---
 Introduction
 * Mailing Lists::
 * Beta Release Schedule::
-* Reporting Problems::
-* Getting the Source::
 Mailing Lists
 * XEmacs Beta Mailing List::
 * XEmacs Patches Mailing List::
 * List Administrivia::
 * Managing your subscription via the Web::
 * Subscribing by e-mail::
 * Unsubscribing by e-mail::
-Compiling Beta XEmacs
+Building Beta XEmacs
+* Getting the Source::
 * Building an XEmacs from patches::
 * Building XEmacs from a full distribution::
 Packages
 @end detailmenu
 @end menu
 @end ifinfo
-@node Introduction, Compiling Beta XEmacs, Top, Top
+@node Introduction, Building Beta XEmacs, Top, Top
 @chapter Introduction
 You are running a potentially unstable version of XEmacs.  Please do
 not report problems with Beta XEmacs to comp.emacs.xemacs.  Report
 them to @uref{mailto:xemacs-beta@@xemacs.org}, preferably with
 @kbd{M-x report-xemacs-bug RET}.
 @menu
 * Mailing Lists::
 * Beta Release Schedule::
-* Reporting Problems::
-* Getting the Source::
 @end menu
 @node Mailing Lists, Beta Release Schedule, Introduction, Introduction
 @section Mailing Lists
 @menu
 * Managing your subscription via the Web::
 * Subscribing by e-mail::
 * Unsubscribing by e-mail::
 @end menu
 @node XEmacs Beta Mailing List, XEmacs Patches Mailing List, Mailing Lists, Mailing Lists
 @subsection XEmacs Beta Mailing List
 If you are not subscribed to the XEmacs beta list you should be.
 Currently all discussion of development issues, including bug reports
 and coding discussion, takes place on the XEmacs Beta mailing list.
 Only patches and administrative actions regarding patches are sent
 elsewhere (to the XEmacs Patches list).
 @node XEmacs Patches Mailing List, XEmacs Design Mailing List, XEmacs Beta Mailing List, Mailing Lists
 @subsection XEmacs Patches Mailing List
 XEmacs Patches records proposed changes to XEmacs, and their
 disposition.  It is open subscription, and all patches that are
 or in the archives.
 Besides patches, only actions by members of the XEmacs Review Board
 should be posted to this list.  All discussion should be redirected to
 XEmacs Beta or XEmacs Design.
 @node XEmacs Design Mailing List, List Administrivia, XEmacs Patches Mailing List, Mailing Lists
 @subsection XEmacs Design Mailing List
 XEmacs Design is for design discussions such as adding major features
 	     @uref{http://list-archive.xemacs.org/xemacs-LIST}
 Note that the xemacs-LIST-admin address is used internally by the
 Mailman software; it is NOT a synonym for xemacs-LIST-request.
 @node Managing your subscription via the Web, Subscribing by e-mail, List Administrivia, Mailing Lists
 @subsection Managing your subscription via the Web
 Subscription, unsubscription, and options (such as digests and
 temporarily suspending delivery) can be accomplished via the web
 interface at @uref{http://www.xemacs.org/Lists/#xemacs-LIST}.
 @node Subscribing by e-mail, Unsubscribing by e-mail, Managing your subscription via the Web, Mailing Lists
 @subsection Subscribing by e-mail
 Send an email message to @uref{mailto:xemacs-LIST-request@@xemacs.org} with
 @samp{subscribe} (without the quotes) as the BODY of the message.
 @node Unsubscribing by e-mail,  , Subscribing by e-mail, Mailing Lists
 @subsection Unsubscribing by e-mail
 Send an email message to @uref{mailto:xemacs-LIST-request@@xemacs.org} with
 @samp{unsubscribe} (without the quotes) as the BODY of the message.
-@node Beta Release Schedule, Reporting Problems, Mailing Lists, Introduction
+@node Beta Release Schedule,  , Mailing Lists, Introduction
 @section Beta Release Schedule
 We would like to achieve a weekly or fortnightly release cycle (you
 know the Open Source model: release early, release often), and in a
 perfect world that would indeed be the case.  There are at least three
 CVS (see @uref{http://www.xemacs.org/Develop/cvsaccess.html}).  If you
 can't use CVS for some reason and must use FTP, please let us know.
 it will make it more likely that we release betas more often.
-@node Reporting Problems, Getting the Source, Beta Release Schedule, Introduction
+@node Building Beta XEmacs, Packages, Introduction, Top
-@section Reporting Problems
+@chapter Building Beta XEmacs
-The best way to get problems fixed in XEmacs is to submit good problem
-reports, @kbd{M-x report-xemacs-bug RET} will help you do this (assuming
-you have a usable XEmacs).  Since this is beta software, problems are
-certain to exist.  Please read through all of part II of the XEmacs
-FAQ for an overview of problem reporting.  Other items which are most
-important are:
-@enumerate
-@item
-Do not submit C stack backtraces without line numbers.  Since it
-is possible to compile optimized with debug information with GCC
-it is never a good idea to compile XEmacs without the -g flag.
-XEmacs runs on a variety of platforms, and often it is not
-possible to recreate problems which afflict a specific platform.
-The line numbers in the C stack backtrace help isolate where the
-problem is actually occurring.
-@item
-Attempt to recreate the problem starting with an invocation of
-XEmacs with @code{xemacs -no-autoloads}.  Quite often, problems are
-due to package interdependencies, and the like.  An actual bug
-in XEmacs should be reproducible in a default configuration
-without loading any special packages (or the one or two specific
-packages that cause the bug to appear).  If you have trouble
-getting anything to work at all with the above invocation, use
-@code{xemacs -vanilla} instead.  If you need to load your user init
-file or the site file to get the problem to occur, then it has
-something to do with them, and you should try to isolate the
-issue in those files.
-@item
-A picture can be worth a thousand words.  When reporting an
-unusual display, it is generally best to capture the problem in a
-screen dump and include that with the problem report.  The easiest
-way to get a screen dump is to use the xv program and its grab
-function.  Save the image as a GIF to keep bandwidth requirements
-down without loss of information.  MIME is the preferred method
-for making the image attachments.
-@end enumerate
-@node Getting the Source,  , Reporting Problems, Introduction
-@section Getting the Source
-In addition to the normal tar distribution, XEmacs source is now
-available via CVS.  Please see
-	    @uref{http://www.xemacs.org/Develop/cvsaccess.html}
-@node Compiling Beta XEmacs, Packages, Introduction, Top
-@chapter Compiling Beta XEmacs
 @menu
+* Getting the Source::
 * Building an XEmacs from patches::
 * Building XEmacs from a full distribution::
 @end menu
-@node Building an XEmacs from patches, Building XEmacs from a full distribution, Compiling Beta XEmacs, Compiling Beta XEmacs
+@node Getting the Source, Building an XEmacs from patches, Building Beta XEmacs, Building Beta XEmacs
+@section Getting the Source
+We provide the traditional tarballs and release-to-release patchkits for
+each beta release.  @xref{Beta Release Schedule}.  These are available
+at
+	    @uref{ftp://ftp.xemacs.org/pub/xemacs/beta/}
+In addition to the normal tar distribution, XEmacs source is now
+available via CVS.  Please see
+	    @uref{http://www.xemacs.org/Develop/cvsaccess.html}
+You can also browse the repository via ViewCVS
+@uref{http://cvs.xemacs.org/}
+@node Building an XEmacs from patches, Building XEmacs from a full distribution, Getting the Source, Building Beta XEmacs
 @section Building an XEmacs from patches
-All beta releases of XEmacs are included with patches from the previous
+All beta releases of XEmacs provide patches from the previous version as
-version in an attempt to keep bandwidth requirements down.  Patches
+an alternative to keep bandwidth requirements down.  These patches are
-should be applied with the GNU patch program in something like the
+actually scripts generated by the @file{makepatch} program, and can be
-following.  Let's say you're upgrading XEmacs 21.5-beta9 to XEmacs
+run if you have the @file{applypatch} program.  Patches may also be
-21.5-beta10 and you have a full unmodified XEmacs 21.5-beta9 source
+applied with the GNU patch program in something like the following.
-tree to work with.  Change to the top level directory and issue the
+Let's say you're upgrading XEmacs 21.5-beta9 to XEmacs 21.5-beta10 and
-shell command:
+you have a full unmodified XEmacs 21.5-beta9 source tree to work with.
+Change to the top level directory and issue the shell command:
 @example
 $ gunzip -c /tmp/xemacs-21.5.9-21.5.10.patch.gz | patch -p1
 @end example
 @end example
 Redirect the output from make to those files because you'll use them
 later when you send off a build report with @kbd{M-x build-report RET}
-@node Building XEmacs from a full distribution,  , Building an XEmacs from patches, Compiling Beta XEmacs
+@node Building XEmacs from a full distribution,  , Building an XEmacs from patches, Building Beta XEmacs
 @section Building XEmacs from a full distribution
 @enumerate
 @item
-Locate a convenient place where you have at least 100MB of free space
+Locate a convenient place where you have at least 200MB of free space
-and issue the command
+(approximately 100MB for sources and compiled Lisp, and 100MB for
+objects and other generated files) and issue the command
 @example
 $ gunzip -c /tmp/xemacs-21.5.10.tar.gz | tar xvf -
 @end example
 @example
 --with-compiler=gcc
 --with-xemacs-compiler=g++
 @end example
-This will compile XEmacs using g++, which will turn on a lot of additional
+This will compile XEmacs using g++, which is generally much stricter
-error-checking.
+about type-checking than C compilers like gcc.
 @item
 If your packages are not installed under /usr/local, you should add a
 line like
 Any other unusual items you feel should be brought to the attention
 of the developers.
 @end enumerate
 @end enumerate
-@node Packages, Improving XEmacs, Compiling Beta XEmacs, Top
+@node Packages, Reporting Problems, Building Beta XEmacs, Top
 @chapter Packages
 [Note: these instructions have been partly updated, but not carefully
 reviewed in some time.  Caveat tester.]
 * Binary package installation::
 * Manual procedures for package management::
 * Building XEmacs and XEmacs packages from scratch::
 @end menu
 @node Binary package installation, Manual procedures for package management, Packages, Packages
 @section Binary package installation
 Prerequisite:  XEmacs 21.0-b1.
 Binary packages are complete entities that can be untarred at the top
 level of an XEmacs package hierarchy and work at runtime.  To install files
 in this directory, run the command @kbd{M-x package-admin-add-binary-package}
 and fill in appropriate values to the prompts.
 @node Manual procedures for package management, Building XEmacs and XEmacs packages from scratch, Binary package installation, Packages
 @section Manual procedures for package management
 Prerequisite: XEmacs 21.0
 @end example
 Of course, being a beta tester, you'd be aware that it is much easier
 to manage your XEmacs packages with PUI.
-@node Building XEmacs and XEmacs packages from scratch,  , Manual procedures for package management, Packages
+@node Building XEmacs and XEmacs packages from scratch, , Manual procedures for package management, Packages
 @section Building XEmacs and XEmacs packages from scratch
 To build everything completely from scratch isn't hard, just time
 consuming.
 @example
 $ make install
 @end example
-@node Improving XEmacs,  Index, Packages, Top
+@node Reporting Problems, Improving XEmacs, Packages, Top
+@section Reporting Problems
+The best way to get problems fixed in XEmacs is to submit good problem
+reports, @kbd{M-x report-xemacs-bug RET} will help you do this (assuming
+you have a usable XEmacs).  Since this is beta software, problems are
+certain to exist.  Please read through all of part II of the XEmacs
+FAQ for an overview of problem reporting.
+@xref{Installation, Installation and Troubleshooting, , xemacs-faq}.
+The most relevant parts are in section 2.4, General Troubleshooting.
+@c #### Why doesn't this link work?
+@c @ref{Q2.4.1, General Troubleshooting, , xemacs-faq}.
+Other items which are most important are:
+@enumerate
+@item
+Do not submit C stack backtraces without line numbers.  Since it
+is possible to compile optimized with debug information with GCC
+it is never a good idea to compile XEmacs without the -g flag.
+XEmacs runs on a variety of platforms, and often it is not
+possible to recreate problems which afflict a specific platform.
+The line numbers in the C stack backtrace help isolate where the
+problem is actually occurring.
+@item
+Attempt to recreate the problem starting with an invocation of
+XEmacs with @code{xemacs -no-autoloads}.  Quite often, problems are
+due to package interdependencies, and the like.  An actual bug
+in XEmacs should be reproducible in a default configuration
+without loading any special packages (or the one or two specific
+packages that cause the bug to appear).  If you have trouble
+getting anything to work at all with the above invocation, use
+@code{xemacs -vanilla} instead.  If you need to load your user init
+file or the site file to get the problem to occur, then it has
+something to do with them, and you should try to isolate the
+issue in those files.
+@item
+A picture can be worth a thousand words.  When reporting an
+unusual display, it is generally best to capture the problem in a
+screen dump and include that with the problem report.  The easiest
+way to get a screen dump is to use the xv program and its grab
+function.  Save the image as a GIF to keep bandwidth requirements
+down without loss of information.  MIME is the preferred method
+for making the image attachments.
+@end enumerate
+@node Improving XEmacs, Index, Reporting Problems, Top
 @chapter Improving XEmacs
 @menu
 * Creating patches for submission::
 * Large contributions::
 @uref{mailto:xemacs-beta@@xemacs.org} and the XEmacs Package Release
 Engineer are the most likely sources of advice.  See
 @uref{http://www.xemacs.org/Develop/jobs.html#package,jobs.html} for
 current information about package release engineers.
 @node Syncing with GNU Emacs,  , New packages, Large contributions
 @subsection Syncing with GNU Emacs
 Syncing with GNU Emacs is an important activity.  Although each
 version has its advantages and areas of concentration, it is very
 @c Print the tables of contents
 @contents
 @c That's all
 @node Index,  , Improving XEmacs, Top
 @unnumbered Index
 @printindex cp

Mercurial > hg > xemacs-beta

comparison man/beta.texi @ 3388:e7fb0df1caea