Mercurial > hg > xemacs-beta

comparison man/xemacs/packages.texi @ 384:bbff43aa5eb7 r21-2-7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2-7
author cvs
date Mon, 13 Aug 2007 11:08:24 +0200
parents a300bb07d72d
children 74fd4e045ea6
comparison
equal deleted inserted replaced
383:6a50c6a581a5 384:bbff43aa5eb7
33 33
34 @item Single-File Packages 34 @item Single-File Packages
35 @cindex single-file packages 35 @cindex single-file packages
36 A single-file package is an aggregate collection of thematically 36 A single-file package is an aggregate collection of thematically
37 related but otherwise independent lisp files. These files are bundled 37 related but otherwise independent lisp files. These files are bundled
38 together for download convenience and individual files may deleted at 38 together for download convenience and individual files may be deleted at
39 will without any loss of functionality. 39 will without any loss of functionality.
40 @end itemize 40 @end itemize
41 41
42 @subsection Package Distributions 42 @subsection Package Distributions
43 43
44 XEmacs Lisp packages are distributed in two ways depending on the 44 XEmacs Lisp packages are distributed in two ways, depending on the
45 intended use. Binary Packages are for installers and end-users and may 45 intended use. Binary Packages are for installers and end-users and may
46 be installed directly into an XEmacs package directory. Source Packages 46 be installed directly into an XEmacs package directory. Source Packages
47 are for developers and include all files necessary for rebuilding 47 are for developers and include all files necessary for rebuilding
48 bytecompiled lisp and creating tarballs for distribution. 48 bytecompiled lisp and creating tarballs for distribution.
49 49
54 54
55 @subsection Source Packages 55 @subsection Source Packages
56 @cindex source packages 56 @cindex source packages
57 Source packages contain all of the Package author's (where appropriate 57 Source packages contain all of the Package author's (where appropriate
58 in regular packages) source code plus all of the files necessary to 58 in regular packages) source code plus all of the files necessary to
59 build distribution tarballs (Unix Tar format files and gzipped for space 59 build distribution tarballs (Unix Tar format files, gzipped for space
60 savings). 60 savings).
61 61
62 @node Using Packages, Building Packages, Package Terminology, Packages 62 @node Using Packages, Building Packages, Package Terminology, Packages
63 @comment node-name, next, previous, up 63 @comment node-name, next, previous, up
64 64
76 non-essential packages were made optional. 76 non-essential packages were made optional.
77 77
78 @subsection Choosing the Packages You Need 78 @subsection Choosing the Packages You Need
79 79
80 The available packages can currently be found in the same ftp directory 80 The available packages can currently be found in the same ftp directory
81 where you grabbed the core distribition from, and are located in the 81 where you grabbed the core distribution from, and are located in the
82 subdirectory @file{packages/binary-packages}. Package file names follow 82 subdirectory @file{packages/binary-packages}. Package file names follow
83 the naming convention @file{<package-name>-<version>-pkg.tar.gz}. 83 the naming convention @file{<package-name>-<version>-pkg.tar.gz}.
84 84
85 If you have EFS @ref{(EFS)}, packages can be installed over the network. 85 If you have EFS @ref{(EFS)}, packages can be installed over the network.
86 Alternatively, if you have copies of the packages locally, you can 86 Alternatively, if you have copies of the packages locally, you can
257 257
258 @subsection Manual Binary Package Installation 258 @subsection Manual Binary Package Installation
259 259
260 Pre-compiled, binary packages can be installed in either a system 260 Pre-compiled, binary packages can be installed in either a system
261 package directory (this is determined when XEmacs is compiled), or in a 261 package directory (this is determined when XEmacs is compiled), or in a
262 subdirectory off your @file{$HOME} directory: 262 subdirectory of your @file{$HOME} directory:
263 263
264 @example 264 @example
265 ~/.xemacs/packages 265 ~/.xemacs/packages
266 @end example 266 @end example
267 267