xemacs-beta: man/xemacs/packages.texi comparison

comparison man/xemacs/packages.texi @ 458:c33ae14dd6d0 r21-2-44

Import from CVS: tag r21-2-44

author	cvs
date	Mon, 13 Aug 2007 11:42:25 +0200
parents	3078fd1074e8
children	0784d089fdc9

comparison

equal deleted inserted replaced

-:4b9290a33024
+:c33ae14dd6d0
 This gives an installer the ability to tailor an XEmacs installation for
 local needs with safe removal of unnecessary code.
 @menu
 * Package Terminology:: Understanding different kinds of packages.
-* Using Packages::      How to install and use packages.
+* Installing Packages:: How to install packages.
-* Building Packages::   Building packages from sources.
+* Building Packages::   Building packages from CVS sources.
+* Local.rules File::    This is an important file don't forget to create/edit it.
 * Creating Packages::   The basics.
-* Available Packages::  A brief, out-of-date, directory of packaged LISP.
+* Available Packages::  A brief directory of packaged LISP.
 @end menu
-@node Package Terminology, Using Packages, , Packages
+@node Package Terminology, Installing Packages, , Packages
 @comment  node-name,  next,  previous,  up
+@heading Package Terminology:
 @subsection Package Flavors
 There are two main flavors of packages.
 @itemize @bullet
 @item Single-File Packages
 @cindex single-file packages
 A single-file package is an aggregate collection of thematically
 related but otherwise independent lisp files.  These files are bundled
 together for download convenience and individual files may be deleted at
-will without any loss of functionality.
+will without any loss of functionality.  However, we would recommend
+that you follow this rule of thumb: "When in doubt, don't delete".
 @end itemize
 @subsection Package Distributions
+@cindex package distributions
 XEmacs Lisp packages are distributed in two ways, depending on the
-intended use.  Binary Packages are for installers and end-users and may
+intended use.  Binary Packages are for installers and end-users that can
 be installed directly into an XEmacs package directory.  Source Packages
 are for developers and include all files necessary for rebuilding
 bytecompiled lisp and creating tarballs for distribution.
 @subsection Binary Packages
 Source packages contain all of the Package author's (where appropriate
 in regular packages) source code plus all of the files necessary to
 build distribution tarballs (Unix Tar format files, gzipped for space
 savings).
-@node Using Packages, Building Packages, Package Terminology, Packages
+Currently, source packages are only available via CVS.  See
-@comment  node-name,  next,  previous,  up
+@url{http://cvs.xemacs.org/} for details.
+@node Installing Packages, Building Packages, Package Terminology, Packages
+@comment  node-name,  next,  previous,  up
+@cindex installing packages
+@cindex install
+@heading Installing Packages:
 @subsection Getting Started
 When you first download XEmacs 21, you will usually first grab the
 @dfn{core distribution},
 @cindex core distribution
 a file called
-@file{xemacs-21.0.tar.gz}. (Replace the @t{21.0} by the current version
+@file{xemacs-21.x.x.tar.gz}. (Replace the @t{21.x.x} by the current version
 number.)  The core distribution contains the sources of XEmacs and a
 minimal set of Emacs Lisp files, which are in the subdirectory named
 @file{lisp}.  This subdirectory used to contain all Emacs Lisp files
 distributed with XEmacs.  Now, to conserve disk space, most
 non-essential packages were made optional.
 @subsection Choosing the Packages You Need
+@cindex choosing packages
-The available packages can currently be found in the same ftp directory
+The @ref{Available Packages} can currently be found in the same ftp directory
 where you grabbed the core distribution from, and are located in the
-subdirectory @file{packages/binary-packages}.  Package file names follow
+subdirectory @file{packages}.  Package file names follow
 the naming convention @file{<package-name>-<version>-pkg.tar.gz}.
 If you have EFS @ref{(EFS)}, packages can be installed over the network.
 Alternatively, if you have copies of the packages locally, you can
 install packages from a local disk or CDROM.
 The file @file{etc/PACKAGES} in the core distribution contains a list of
-the packages available at the time of the XEmacs release.  Packages are
+the @ref{Available Packages} at the time of the XEmacs release.  Packages are
 also listed on the @code{Options} menu under:
 @example
-Options->Customize->Emacs->Packages
+Options -> Customize -> Emacs -> Packages
 @end example
 However, don't select any of these menu picks unless you actually want
 to install the given package (and have properly configured your system
 to do so).
 You can also get a list of available packages, and whether or not they
 are installed, using the visual package browser and installer.  You can
 access it via the menus:
 @example
-Options->Manage Packages->List & Install
+Options -> Manage Packages -> List & Install
 @end example
 Or, you can get to it via the keyboard:
 @example
 @example
 M-x package-get-package-provider RET thingatpt
 @end example
-which will return something like (fsf-compat "1.06"). You can the use
+which will return something like (fsf-compat "1.08"). You can the use
 one of the methods above for installing the package you want.
 @subsection XEmacs and Installing Packages
-Normally, packages are installed over the network, using EFS
+There are three main ways to install packages:
-@ref{(EFS)}.  However, you may not have network access, or you may
-already have some or all of the packages on a local disk, such as a
+@menu
-CDROM.  If you want to install from a local disk, you must first tell
+* Sumo::              All at once, using the 'Sumo Tarball'.
-XEmacs where to find the package binaries.  This is done by adding a line
+* Manually::          Using individual package tarballs.
-like the following to your init file:
+* Automatically::     Using the package tools from XEmacs.
+* Which Packages::    Which packages to install.
-@example
+* Removing Packages:: Removing packages.
-(setq package-get-remote (cons (list nil "/my/path/to/package/binaries")
+@end menu
-package-get-remote))
-@end example
+But regardless of the method you use to install packages, they can only
+be used by XEmacs after a restart.
-@xref{Init File}.
+@node Sumo, Manually, ,Installing Packages
-Here, you'd change @file{/my/path/to/package/binaries} to be the path
+@comment  node-name,  next,  previous,  up
-to your local package binaries.  Next, restart XEmacs, and you're ready
+@cindex sumo package install
-to go (advanced users can just re-evaluate the sexp).
+@heading Installing the Sumo Packages:
+Those with little time, cheap connections and plenty of disk space can
-If you are installing from a temporary, one-time directory, you can also
+install all the packages at once using the sumo tarballs.
-add these directory names to @code{package-get-remote} using:
+Download the file: @file{xemacs-sumo.tar.gz}
-@example
+For an XEmacs compiled with Mule you also need: @file{xemacs-mule-sumo.tar.gz}
-M-x pui-add-install-directory
-@end example
+N.B. They are called 'Sumo Tarballs' for good reason. They are
+currently about 19MB and 4.5MB (gzipped) respectively.
-Note, however, that any directories added using this function are not
-saved; this information will be lost when you quit XEmacs.
+Install them by:
-If you're going to install over the network, you only have to insure
+@code{cd $prefix/lib/xemacs ; gunzip -c <tarballname> | tar xvf - RET}
-that EFS @ref{(EFS)} works, and that it can get outside a firewall, if
-you happen to be behind one.  You shouldn't have to do anything else;
+Or, if you have GNU tar:
-XEmacs already knows where to go. However you can add your own mirrors
-to this list. See @code{package-get-remote}.
+@code{cd $prefix/lib/xemacs ; tar zxvf /path/to/<tarballname> RET}
-The easiest way to install a package is to use the visual package
+As the Sumo tarballs are not regenerated as often as the individual
-browser and installer, using the menu pick:
+packages, it is recommended that you use the automatic package tools
+afterwards to pick up any recent updates.
-@example
-Options->Manage Packages->List & Install
+@node Manually, Automatically, Sumo, Installing Packages
-@end example
+@comment  node-name,  next,  previous,  up
-or
+@cindex manual package install
-@example
+@heading Manual Package Installation:
-Options->Manage Packages->Using Custom->Select-> ...
+Fetch the packages from the FTP site, CD-ROM whatever. The filenames
-@end example
+have the form @file{name-<version>-pkg.tar.gz} and are gzipped tar files. For
+a fresh install it is sufficient to untar the file at the top of the
-You can also access it using the keyboard:
+package hierarchy.
-@example
+Note: If you are upgrading packages already installed, it's best to
-M-x pui-list-packages
+remove the old package first @ref{Removing Packages}.
-@end example
+For example if we are installing the @file{xemacs-base}
+package (version 1.48):
+@example
+mkdir $prefix/lib/xemacs/xemacs-packages RET # if it does not exist yet
+cd $prefix/lib/xemacs/xemacs-packages RET
+gunzip -c /path/to/xemacs-base-1.48-pkg.tar.gz | tar xvf - RET
+Or if you have GNU tar, the last step can be:
+tar zxvf /path/to/xemacs-base-1.48-pkg.tar.gz RET
+@end example
+For MULE related packages, it is best to untar into the mule-packages
+hierarchy, i.e. for the @file{mule-base} package, version 1.37:
+@example
+mkdir $prefix/lib/xemacs/mule-packages RET # if it does not exist yet
+cd $prefix/lib/xemacs/mule-packages RET
+gunzip -c /path/to/mule-base-1.37-pkg.tar.gz | tar xvf - RET
+Or if you have GNU tar, the last step can be:
+tar zxvf /path/to/mule-base-1.37-pkg.tar.gz RET
+@end example
+@node Automatically, Which Packages ,Manually, Installing Packages
+@comment  node-name,  next,  previous,  up
+@cindex automatic package install
+@cindex package tools
+@heading Automatic Package Installation:
+XEmacs comes with some tools to make the periodic updating and
+installing easier. It will notice if new packages or versions are
+available and will fetch them from the FTP site.
+Unfortunately this requires that a few packages are already in place.
+You will have to install them by hand as above or use a SUMO tarball.
+This requirement will hopefully go away in the future. The packages
+you need are:
+@example
+efs          - To fetch the files from the FTP site or mirrors.
+xemacs-base  - Needed by efs.
+and optionally:
+mule-base    - Needed if you want to use XEmacs with MULE.
+@end example
+After installing these by hand, fire up XEmacs and follow these
+steps.
+Note: The menus in XEmacs 21.2.x and up have changed slightly, so
+where I mention "Options -> Manage Packages", substitute "Tools ->
+Packages".
+@enumerate 1
+@item Choose a download site.
+via menu: Options -> Manages Packages -> Add Download Site
+via keyb: @code{M-x customize-variable RET package-get-remote RET}
+(put in the details of remote host and directory)
+If the package tarballs _AND_ the package-index file are in a
+local directory, you can: @code{M-x pui-add-install-directory RET}
+@item Obtain a list of packages and display the list in a buffer named
+@file{*Packages*}.
+menu: Options -> Manage Packages -> List & Install
+keyb: @code{M-x pui-list-packages RET}
+XEmacs will now connect to the remote site and download the
+latest package-index file.  If you see an error about the
+package-index entries not being PGP signed, you can safely
+ignore this because PGP has not been integrated into the XEmacs
+package tools yet.
 The visual package browser will then display a list of all packages.
 Help information will be displayed at the very bottom of the buffer; you
 may have to scroll down to see it.  You can also press @kbd{?} to get
 the same help.  From this buffer, you can tell the package status by the
 @end table
 Moving the mouse over a package will also cause additional information
 about the package to be displayed in the minibuffer.
-@subsection Other package installation interfaces
+@item Choose the packages you wish to install.
-For an alternative package interface, you can select packages from the
+mouse: Click button 2 on the package name.
-customize menus, under:
+keyb: @kbd{RET} on the package name
-@example
+@item Make sure you have everything you need.
-Options->Customize->Emacs->Packages-> ...
+menu: Packages -> Add Required
-@end example
+keyb: @kbd{r}
-or
-@example
+XEmacs will now search for packages that are required by the
-Options->Manage Packages->Using Custom->Select-> ...
+ones that you have chosen to install and offer to select
-@end example
+those packages also.
-Set their state to on, and then do:
+For novices and gurus alike, this step can save your bacon.
+It's easy to forget to install a critical package.
-@example
-Options->Manage Packages->Using Custom->Update Packages
+@item Download and install the packages.
-@end example
+menu: Packages -> Install/Remove Selected
+keyb: @kbd{x}
-This will automatically retrieve the packages you have selected from the
+@end enumerate
-XEmacs ftp site or your local disk, and install them into
-XEmacs.  Additionally it will update any packages you already have
-installed to the newest version.  Note that if a package is newly
-installed you will have to restart XEmacs for the change to take effect.
 You can also install packages using a semi-manual interface:
 @example
 M-x package-get-all <return>
 @end example
 Enter the name of the package (e.g., @code{prog-modes}), and XEmacs
-will search for the latest version (as listed in the lisp file
+will search for the latest version and install it and any packages that
-@file{lisp/package-get-base.el}), and install it and any packages that
 it depends upon.
-@subsection Manual Binary Package Installation
+@node Which Packages, Removing Packages, Automatically, Installing Packages
+@comment  node-name,  next,  previous,  up
-Pre-compiled, binary packages can be installed in either a system
+@cindex which packages
-package directory (this is determined when XEmacs is compiled), or in
+@cindex choosing packages
-one of the following
+@heading Which Packages to Install:
-subdirectories of your @file{$HOME} directory:
+This is difficult to say. When in doubt install a package. If you
+administrate a big site it might be a good idea to just install
-@example
+everything. A good minimal set of packages for XEmacs-latin1 would be
-~/.xemacs/mule-packages
-~/.xemacs/xemacs-packages
+xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
-@end example
+edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes,
+text-modes, time
-Packages in the former directory will only be found by a Mule-enabled
-XEmacs.
+If you are using the XEmacs package tools, don't forget to do:
-XEmacs does not have to be running to install binary packages, although
+	Packages -> Add Required
-XEmacs will not know about any newly-installed packages until you
-restart XEmacs.  Note, however, that installing a newer version of a
+To make sure you have everything that the packages you have chosen to
-package while XEmacs is running could cause strange errors in XEmacs;
+install need.
-it's best to exit XEmacs before upgrading an existing package.
+See also @ref{Available Packages} for further descriptions of the individual
-To install binary packages manually:
+packages.
-@enumerate
+@node Removing Packages, ,Which Packages, Installing Packages
-@item
+@comment  node-name,  next,  previous,  up
-Download the package(s) that you want to install.  Each binary package
+@cindex removing packages
-will typically be a gzip'd tarball.
+@cindex deleting packages
+@heading Removing Packages:
-@item
+Because the exact files and their locations contained in a package may
-Decide where to install the packages: in the system package
+change it is recommended to remove a package first before installing a
-directory, or in @file{~/.xemacs/mule-packages} or
+new version. In order to facilitate removal each package contains an
-@file{~/.xemacs/xemacs-packages}, respectively.  If you want to install
+@file{pgkinfo/MANIFEST.pkgname} file which list all the files belonging
-the packages in the system package directory, make sure you can write
+to the package.
-into that directory.  If you want to install in your @file{$HOME}
-directory, create the directory, @file{~/.xemacs/mule-packages} or
+No need to panic, you don't have to go through the
-@file{~/.xemacs/xemacs-packages}, respectively.
+@file{pkinfo/MANIFEST.pkgname} and manually delete the files.  Instead, use
+@code{M-x package-admin-delete-binary-package RET}.
-@item
-Next, @code{cd} to the directory under which you want to install the
+Note that the interactive package tools included with XEmacs already do
-package(s).
+this for you.
-@item
+@node Building Packages, Local.rules File, Installing Packages, Packages
-From this directory, uncompress and extract each of the gzip'd tarballs
+@comment  node-name,  next,  previous,  up
-that you downloaded in step 1.  Unix and Cygnus cygwin users will
+@cindex building packages
-typically do this using the commands:
+@cindex package building
+@heading Building Packages:
-@example
+Currently, source packages are only available via anonymous CVS.  See
-gunzip < package.tar.gz | tar xvf -
+@url{http://cvs.xemacs.org/} for details of checking out the
-@end example
+@file{xemacs-packages} module.
-Above, replace @file{package.tar.gz} with the filename of the
-package that you downloaded in step 1.
-Of course, if you use GNU @code{tar}, you could also use:
-@example
-tar xvzf package.tar.gz
-@end example
-@comment What about native MS Windows users???
-@item
-That's it.  Quit and restart XEmacs to get it to recognize any new or
-changed packages.
-@end enumerate
-@node Building Packages, Creating Packages, Using Packages, Packages
-@comment  node-name,  next,  previous,  up
-Source packages are available from the @file{packages/source-packages}
-subdirectory of your favorite XEmacs distribution site.  Alternatively,
-they are available via CVS from @file{cvs.xemacs.org}.  Look at
-@file{http://cvs.xemacs.org} for instructions.
 @subsection Prerequisites for Building Source Packages
-You must have GNU @code{cp}, GNU @code{install} (or a BSD compatible
+@table @code
-@code{install} program) GNU @code{make} (3.75 or later preferred),
+@item GNU cp
-@code{makeinfo} (1.68 from @code{texinfo-3.11} or later required), GNU
+@item GNU ginstall
-@code{tar} and XEmacs 21.0.  The source packages will untar into a
+(or a BSD compatible install program).
-correct directory structure.  At the top level you must have
+@item GNU make
-@file{XEmacs.rules} and @file{package-compile.el}.  These files are
+(3.75 or later preferred).
-available from the XEmacs FTP site from the same place you obtained your
+@item makeinfo
-source package distributions.
+(1.68 from texinfo-3.11 or later required).
+@item GNU tar
+(or equivalent).
+@item GNU gzip
+(or equivalent).
+@item A properly configured @file{Local.rules} file.
+@ref{Local.rules File}.
+@end table
+And of course, XEmacs 21.0 or higher.
 @subsection What You Can Do With Source Packages
-NB:  A global build operation doesn't exist yet as of 13 January 1998.
+The packages CVS sources are most useful for creating XEmacs package
+tarballs for installation into your own XEmacs installations or for
-Source packages are most useful for creating XEmacs package tarballs
-for installation into your own XEmacs installations or for
 distributing to others.
 Supported operations from @file{make} are:
 @table @code
-@item clean
-Remove all built files except @file{auto-autoloads.el} and @file{custom-load.el}.
-@item distclean
-Remove XEmacs backups as well as the files deleted by @code{make clean}.
 @item all
 Bytecompile all files, build and bytecompile byproduct files like
 @file{auto-autoloads.el} and @file{custom-load.el}.  Create info version
 of TeXinfo documentation if present.
+@item bindist
+Does a @code{make all} as well as create a binary package tarball in the
+staging directory.
+@item install
+Bytecompile all files, build and bytecompile byproduct files like
+@file{auto-autoloads.el} and @file{custom-load.el}.  Create info version
+of TeXinfo documentation if present.  And install everything into the
+staging directory.
 @item srckit
 Usually aliased to @code{srckit-std}.  This does a @code{make
 distclean} and creates a package source tarball in the staging
 directory.  This is generally only of use for package maintainers.
 @item dist
 Runs the rules @code{srckit} followed by @code{binkit}.  This is
 primarily of use by XEmacs maintainers producing files for distribution.
-@end table
+@item clean
+Remove all built files except @file{auto-autoloads.el} and @file{custom-load.el}.
-@node Creating Packages, Available Packages, Building Packages, Packages
-@comment  node-name,  next,  previous,  up
+@item distclean
+Remove all created files.
+@end table
+@node Local.rules File, Creating Packages, Building Packages, Packages
+@comment  node-name,  next,  previous,  up
+@cindex local.rules
+@heading The Local.rules File:
+This file is used when building and installing packages from source.  In
+the top level of the CVS module, @file{xemacs-packages}, contains the
+file, @file{Local.rules.template}.  Simply copy that to
+@file{Local.rules} and edit it to suit your needs.
+These are the variables in 'Local.rules' that you will need to
+address.
+@table @var
+@item symlink =
+Set this to 't' if you want to do a "run in place".
+Setting this doesn't work well with 'make bindist'
+@item XEMACS_PACKAGES =
+This is where you set the normal packages that you
+want to install. eg:
+@example
+XEMACS_PACKAGES = libs/xemacs-base comm/bbdb
+@end example
+@item XEMACS_STAGING = $@{XEMACS_PACKAGES_BASE@}/../Packages
+Set this to where you want normal packages to be
+installed to.
+@item PACKAGE_INDEX = package-index
+If you want the package-index file to have a different
+name, change this.
+@item BUILD_WITHOUT_MULE =
+Building from CVS defaults to building the Mule
+packages.  Set this to 't' if you don't want/have Mule
+@item MULE_PACKAGES =
+Same as for 'XEMACS_PACKAGES' except you list the Mule
+packages you want to install here. eg:
+@example
+MULE_PACKAGES = mule/mule-base mule/skk
+@end example
+@item MULE_STAGING = $@{XEMACS_PACKAGES_BASE@}/../Mule-Packages
+Set this to where you want Mule packages installed
+to.  Note:  'make bindist' does not use this variable.
+@item XEMACS = xemacs
+If your XEmacs isn't in your path, change this.
+@item XEMACS_NATIVE_NT =
+Set this to 't' if you are building on WinNT.
+@item INSTALL = install -c
+The path to your BSD compatible install program.
+@item TAR = tar
+The path to your tar program
+@item BZIP2 =
+If you want bzip2 tarballs, set this.
+@item MAKEINFO = makeinfo
+The path to your makeinfo program
+@end table
+@node Creating Packages, Available Packages, Local.rules File, Packages
+@comment  node-name,  next,  previous,  up
+@cindex creating packages
+@heading Creating Packages:
 Creating a package from an existing Lisp library is not very difficult.
 In addition to the Lisp libraries themselves, you need a
 @file{package-info.in} file and a simple @file{Makefile}.  The rest is
 done by @file{XEmacs.rules}, part of the packaging system
 packages have needs beyond the basic templates.  See @file{XEmacs.rules}
 or a future revision of this manual for details.
 @node Available Packages,  , Creating Packages, Packages
 @comment  node-name,  next,  previous,  up
+@cindex available packages
-This section is surely out-of-date.  If you're sure that XEmacs is
+@cindex packages
-able to do something, but your installed XEmacs won't do it for you,
+@heading Available Packages:
-it's probably in a package.  If you can't find it in this section,
+This section lists the Lisp packages that are currently available from
-that's a bug---please report it.  It is very hard to keep this section
+xemacs.org and it's mirrors.  If a particular package that you are
-up-to-date; your reports, comments, and questions will help a lot.
+looking for isn't here, please send a message to the
+@email{xemacs-beta@@xemacs.org, XEmacs Beta list}.
-This data is up-to-date as of 10 February 1999.  (Ouch!  I told you!)
+This data is up-to-date as of January 17, 2001.
 @subsection Library Packages (libs)
 These packages are required to build and support most of the rest of
 XEmacs.  By design, xemacs-base is a `regular' package.  Use restraint
 Support for Sparcworks.
 @item apel
 A Portable Emacs Library.  Used by XEmacs MIME support.
-@item edebug
-A Lisp debugger.
 @item dired
 The DIRectory EDitor is for manipulating, and running commands on
 files in a directory.
+@item edebug
+A Lisp debugger.
 @item efs
 Treat files on remote systems the same as local files.
+@item elib
+Portable Emacs Lisp utilities library.
+@item fsf-compat
+FSF Emacs compatibility files.
 @item mail-lib
 Fundamental lisp files for providing email support.
+@item sounds-au
+XEmacs Sun sound files.
+@item sounds-wav
+XEmacs Microsoft sound files.
 @item tooltalk
 Support for building with Tooltalk.
 @item xemacs-base
 These packages provide support for various communications, primarily
 email and usenet.
 @table @file
+@item bbdb
+The Big Brother Data Base
+@item eicq
+ICQ Client developed and tested on Linux x86;
+only supported on that platform
+@item eudc
+Emacs Unified Directory Client (LDAP, PH).
 @item footnote
 Footnoting in mail message editing modes.
 @item gnats
 XEmacs bug reports.
 @item gnus
 The Gnus Newsreader and Mailreader.
 @item mailcrypt
 Support for messaging encryption with PGP.
+@item mew
+Messaging in an Emacs World.
 @item mh-e
 Front end support for MH.
 @item net-utils
 Miscellaneous Networking Utilities.  This is a single-file package and
 files may be deleted at will.
-@item ph
-Emacs implementation of the ph client to CCSO/qi directory servers.
 @item rmail
 An obsolete Emacs mailer.  If you do not already use it don't start.
 @item supercite
 An Emacs citation tool.  Useful with all Emacs Mailers and Newsreaders.
 @item tm
-Emacs MIME support.
+Emacs MIME support. Not needed for Gnus >= 5.8.0
 @item vm
 An Emacs mailer.
 @item w3
 A Web browser.
+@item zenirc
+ZENIRC IRC Client.
 @end table
 @subsection Games and Amusements (games)
+All work and no play...
 @table @file
 @item cookie
 Spook and Yow (Zippy quotes).
 Other amusements and diversions.
 @end table
 @subsection Mule Support (mule)
+MULti-lingual Enhancement.  Support for world scripts such as
+Latin, Arabic, Cyrillic, Chinese, Japanese, Greek, Hebrew etc.
+To use these packages your XEmacs must be compiled with Mule
+support.
 @table @file
+@item edict
+Lisp Interface to EDICT, Kanji Dictionary.
 @item egg-its
 Wnn (4.2 and 6) support.  SJ3 support.  Must be installed prior to
 XEmacs build.
 @item leim
 @item locale
 Used for localized menubars (French and Japanese) and localized splash
 screens (Japanese).
+@item lookup
+Dictionary support. (This isn't an English dictionary program)
 @item mule-base
 Basic Mule support.  Must be installed prior to building with Mule.
 @item skk
 Another Japanese Language Input Method.  Can be used without a
 separate process running as a dictionary server.
 @end table
 @subsection Productivity Packages (oa)
+Things to make life a little easier.
 @table @file
+@item calc
+Emacs calculator.
 @item calendar
 Calendar and diary support.
 @item edit-utils
 Single file lisp packages for various XEmacs goodies.  Load this and
 weed out the junk you don't want.
 @item forms
-Forms editing support (obsolete, use the builtin Widget instead).
+Forms editing support (obsolete, use the built-in Widget instead).
 @item frame-icon
 Provide a WM icon based on major mode.
 @item hm--html-menus
 @item slider
 User interface tool.
 @item speedbar
-??? Document me.
+Provides a separate frame with convenient references.
 @item strokes
 Mouse enhancement utility.
 @item text-modes
 Display time & date on the modeline.
 @end table
 @subsection Operating System Utilities (os)
+Tools for working with the operating system.
 @table @file
+@item eshell
+Command shell implemented entirely in Emacs Lisp.
 @item eterm
 Terminal emulator.
 @item igrep
 Enhanced front-end for Grep.
 @item os-utils
 Miscellaneous single-file O/S utilities, for printing, archiving,
 compression, remote shells, etc.
+@item pcomplete
+Provides programmatic completion.
+@item ps-print-nomule
+Old, but no-Mule safe ps-print.
 @item view-process
 A Unix process browsing tool.
 @end table
 @subsection Program Editing Support (prog)
+XEmacs supports a multitude of programming languages.  These
+packages will help your coding.
 @table @file
 @item ada
 Ada language support.
 Interface over patch.
 @item emerge
 Another interface over patch.
+@item idlwave
+Editing and Shell mode for the Interactive Data Language.
+@item jde
+Java language and development support.
 @item pcl-cvs
 CVS frontend.
 @item prog-modes
-Miscellaneous Lisp libraries for various programming languages.
+Miscellaneous single-file lisp files for various programming languages.
 @item scheme
 Front-end support for Inferior Scheme.
+@item semantic
+Semantic bovinator.
 @item sh-script
 Support for editing shell scripts.
 @item vc
-Version control for free systems.
+Version Control for Free systems.
 @item vc-cc
-Version control for ClearCase.
+Version Control for ClearCase.  This package will shortly be
+replaced with clearcase.el
 @item vhdl
 Support for VHDL.
 @end table
 @subsection Word Processing (wp)
+Working with text.
 @table @file
 @item auctex
 Basic TeX/LaTeX support.
 Crisp/Brief emulation.
 @item edt
 DEC EDIT/EDT emulation.
+@item reftex
+Emacs support for LaTeX cross-references, citations.
 @item texinfo
 XEmacs TeXinfo support.
 @item textools
 Single-file TeX support.

Mercurial > hg > xemacs-beta

comparison man/xemacs/packages.texi @ 458:c33ae14dd6d0 r21-2-44