Source

xemacs-21.4 / README.packages

Diff from to

File README.packages

 ------------------------
 
 Q. Do I need to have the packages to compile XEmacs?
-A. No, XEmacs will build and install just fine without any packages
-   installed.  However, only the most basic editing functions will be
-   available with no packages installed, so installing packages is an
-   essential part of making your installed XEmacs _useful_.
+A. If you want to compile with MULE, you need the mule-base package installed.
+   Otherwise, no package is required before compilation.
 
 Q. I really liked the old way that packages were bundled and do not
    want to mess with packages at all.
 A. You can grab all the packages at once like you used to with old
    XEmacs versions, skip to the 'Sumo Tarball' section below.
 
-Q. After installing, I want XEmacs to do `foo', but when I invoke it
-   (or click the toolbar button or select the menu item), nothing (or
-   an error) happens, and it used to work.
-A. See the first FAQ; you may be missing a package that is essential to
-   you.  You can either track it down and install it, or install the
-   `Sumo Tarball' (see the second FAQ).
-
 A note of caution
 -----------------
 
 -------------------------
 
 Packages are available from ftp://ftp.xemacs.org/pub/xemacs/packages
-and its mirrors.
+and its mirror.
 
 How to install the packages
 ---------------------------
 ----------------
 
 Those with little time, cheap connections and plenty of disk space can
-install all the packages at once using the sumo tarballs.
-Download the file
+install all packages at once using the sumo tarballs.
+Download the files
 
-xemacs-sumo.tar.gz
+xemacs-sumo-<date>.tar.gz if you have a latin-1 XEmacs.
 
-For an XEmacs compiled with Mule you also need
+or
 
-xemacs-mule-sumo.tar.gz
+xemacs-mule-sumo-<date>.tar.gz if you have a MULE XEmacs.
 
-N.B. They are called 'Sumo Tarballs' for good reason. They are
-currently about 15MB and 2.3MB (gzipped) respectively.
+N.B. There are called 'Sumo Tarballs' for good reason. They are
+currently 15MB and 23MB (gzipped) respectively.
 
 Install them by
 
 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. 
+Unfortunately this requires that a few packages are alreadyin 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:
 
    mailcrypt    - If you have PGP installed and want to verify the
                   signature of the index file.
-   mule-base    - Needed if you want to use XEmacs with MULE.
+   mule-base    - Needed if you want to compile XEmacs with MULE.
 
 After installing these by hand, you can start XEmacs. (It is a good
 idea to use 'xemacs -vanilla' here as your startup files might need
 Note to MULE users
 ------------------
 
-It is a good idea to keep packages that are MULE-only separate by
-putting them in the mule-packages hierarchy.  Non-Mule XEmacsen will
-ignore packages in mule-packages so it is safe to have that directory
-in the package path of a Non-Mule XEmacs.
+Unlike all other packages the mule-base package is used at build/dump 
+time. This means that you need this available before compiling XEmacs
+with MULE. Also it is a good idea to keep packages that are
+MULE-only separate by putting them in the mule-packages hierarchy.
 
 Which Packages to install?
 --------------------------
 See also '.../etc/PACKAGES' for further descriptions of the individual
 packages (currently outdated).
 
-Finding the Right Packages
---------------------------
-
-If you want to find out which package contains the functionality you
-are looking for, use M-x package-get-package-provider, and give it a
-symbol that is likely to be in that package.  For example, if some
-code you want to use has a (require 'thingatpt) in it, try doing
-M-x package-get-package-provider RET thingatpt , which will return
-something like: (fsf-compat "1.06").
-
 Upgrading/Removing Packages
 ---------------------------
 
 As the exact files and their locations contained in a package may
-change it is recommended to remove a package first before installing a
+change it is recommend to remove a package first before installing a
 new version. In order to facilitate removal each package contains an
 pgkinfo/MANIFEST.pkgname file which list all the files belong to the
 package. M-x package-admin-delete-binary-package RET can be used to
 ------------------------
 
 In addition to the system wide packages, each user can have his own
-packages installed in "~/.xemacs" (Note that this will most likely
-change to "~/.xemacs/packages" in the near future). If you want to
+packages installed in "./xemacs" (Note that this will most likely
+change to "./xemacs/packages" in the near future). If you want to
 install packages there using the interactive tools, you need to set
-'pui-package-install-dest-dir' to "~/.xemacs"
+'pui-package-install-dest-dir' to "/xemacs"
 
 Site lisp/Site start
 --------------------