|
444
|
1 @c This is part of the XEmacs manual.
|
|
|
2 @c Copyright (C) 1985, 86, 87, 93, 94, 95, 1997 Free Software Foundation, Inc.
|
|
|
3 @c See file xemacs.texi for copying conditions.
|
|
|
4 @node Packages, Basic, Startup Paths, Top
|
|
428
|
5 @comment node-name, next, previous, up
|
|
|
6
|
|
|
7 @section Packages
|
|
|
8 @cindex packages
|
|
|
9
|
|
|
10 The XEmacs 21 distribution comes only with a very basic set of
|
|
|
11 built-in modes and packages. Most of the packages that were part of
|
|
|
12 the distribution of earlier versions of XEmacs are now available
|
|
|
13 separately. The installer as well as the user can choose which
|
|
|
14 packages to install; the actual installation process is easy.
|
|
|
15 This gives an installer the ability to tailor an XEmacs installation for
|
|
|
16 local needs with safe removal of unnecessary code.
|
|
|
17
|
|
|
18 @menu
|
|
|
19 * Package Terminology:: Understanding different kinds of packages.
|
|
|
20 * Using Packages:: How to install and use packages.
|
|
|
21 * Building Packages:: Building packages from sources.
|
|
448
|
22 * Creating Packages:: The basics.
|
|
444
|
23 * Available Packages:: A brief, out-of-date, directory of packaged LISP.
|
|
428
|
24 @end menu
|
|
|
25
|
|
|
26 @node Package Terminology, Using Packages, , Packages
|
|
|
27 @comment node-name, next, previous, up
|
|
|
28
|
|
|
29 @subsection Package Flavors
|
|
|
30
|
|
|
31 There are two main flavors of packages.
|
|
|
32
|
|
|
33 @itemize @bullet
|
|
|
34 @item Regular Packages
|
|
|
35 @cindex regular packages
|
|
|
36 A regular package is one in which multiple files are involved and one
|
|
|
37 may not in general safely remove any of them.
|
|
|
38
|
|
|
39 @item Single-File Packages
|
|
|
40 @cindex single-file packages
|
|
|
41 A single-file package is an aggregate collection of thematically
|
|
|
42 related but otherwise independent lisp files. These files are bundled
|
|
|
43 together for download convenience and individual files may be deleted at
|
|
|
44 will without any loss of functionality.
|
|
|
45 @end itemize
|
|
|
46
|
|
|
47 @subsection Package Distributions
|
|
|
48
|
|
|
49 XEmacs Lisp packages are distributed in two ways, depending on the
|
|
|
50 intended use. Binary Packages are for installers and end-users and may
|
|
|
51 be installed directly into an XEmacs package directory. Source Packages
|
|
|
52 are for developers and include all files necessary for rebuilding
|
|
|
53 bytecompiled lisp and creating tarballs for distribution.
|
|
|
54
|
|
|
55 @subsection Binary Packages
|
|
|
56 @cindex binary packages
|
|
|
57 Binary packages may be installed directly into an XEmacs package
|
|
|
58 hierarchy.
|
|
|
59
|
|
|
60 @subsection Source Packages
|
|
|
61 @cindex source packages
|
|
|
62 Source packages contain all of the Package author's (where appropriate
|
|
|
63 in regular packages) source code plus all of the files necessary to
|
|
|
64 build distribution tarballs (Unix Tar format files, gzipped for space
|
|
|
65 savings).
|
|
|
66
|
|
|
67 @node Using Packages, Building Packages, Package Terminology, Packages
|
|
|
68 @comment node-name, next, previous, up
|
|
|
69
|
|
|
70 @subsection Getting Started
|
|
|
71
|
|
|
72 When you first download XEmacs 21, you will usually first grab the
|
|
|
73 @dfn{core distribution},
|
|
|
74 @cindex core distribution
|
|
|
75 a file called
|
|
|
76 @file{xemacs-21.0.tar.gz}. (Replace the @t{21.0} by the current version
|
|
|
77 number.) The core distribution contains the sources of XEmacs and a
|
|
|
78 minimal set of Emacs Lisp files, which are in the subdirectory named
|
|
|
79 @file{lisp}. This subdirectory used to contain all Emacs Lisp files
|
|
|
80 distributed with XEmacs. Now, to conserve disk space, most
|
|
|
81 non-essential packages were made optional.
|
|
|
82
|
|
|
83 @subsection Choosing the Packages You Need
|
|
|
84
|
|
|
85 The available packages can currently be found in the same ftp directory
|
|
|
86 where you grabbed the core distribution from, and are located in the
|
|
|
87 subdirectory @file{packages/binary-packages}. Package file names follow
|
|
|
88 the naming convention @file{<package-name>-<version>-pkg.tar.gz}.
|
|
|
89
|
|
|
90 If you have EFS @ref{(EFS)}, packages can be installed over the network.
|
|
|
91 Alternatively, if you have copies of the packages locally, you can
|
|
|
92 install packages from a local disk or CDROM.
|
|
|
93
|
|
|
94 The file @file{etc/PACKAGES} in the core distribution contains a list of
|
|
|
95 the packages available at the time of the XEmacs release. Packages are
|
|
|
96 also listed on the @code{Options} menu under:
|
|
|
97
|
|
|
98 @example
|
|
440
|
99 Options->Customize->Emacs->Packages
|
|
428
|
100 @end example
|
|
|
101
|
|
|
102 However, don't select any of these menu picks unless you actually want
|
|
|
103 to install the given package (and have properly configured your system
|
|
|
104 to do so).
|
|
|
105
|
|
|
106 You can also get a list of available packages, and whether or not they
|
|
|
107 are installed, using the visual package browser and installer. You can
|
|
|
108 access it via the menus:
|
|
|
109
|
|
|
110 @example
|
|
440
|
111 Options->Manage Packages->List & Install
|
|
428
|
112 @end example
|
|
|
113
|
|
|
114 Or, you can get to it via the keyboard:
|
|
|
115
|
|
|
116 @example
|
|
|
117 M-x pui-list-packages
|
|
|
118 @end example
|
|
|
119
|
|
|
120 Hint to system administrators of multi-user systems: it might be a good
|
|
|
121 idea to install all packages and not interfere with the wishes of your
|
|
|
122 users.
|
|
|
123
|
|
|
124 If you can't find which package provides the feature you require, try
|
|
|
125 using the @code{package-get-package-provider} function. Eg., if you know
|
|
|
126 that you need @code{thingatpt}, type:
|
|
|
127
|
|
|
128 @example
|
|
|
129 M-x package-get-package-provider RET thingatpt
|
|
|
130 @end example
|
|
|
131
|
|
|
132 which will return something like (fsf-compat "1.06"). You can the use
|
|
|
133 one of the methods above for installing the package you want.
|
|
|
134
|
|
|
135 @subsection XEmacs and Installing Packages
|
|
|
136
|
|
|
137 Normally, packages are installed over the network, using EFS
|
|
|
138 @ref{(EFS)}. However, you may not have network access, or you may
|
|
|
139 already have some or all of the packages on a local disk, such as a
|
|
|
140 CDROM. If you want to install from a local disk, you must first tell
|
|
|
141 XEmacs where to find the package binaries. This is done by adding a line
|
|
442
|
142 like the following to your init file:
|
|
428
|
143
|
|
|
144 @example
|
|
|
145 (setq package-get-remote (cons (list nil "/my/path/to/package/binaries")
|
|
|
146 package-get-remote))
|
|
|
147 @end example
|
|
|
148
|
|
442
|
149 @xref{Init File}.
|
|
|
150
|
|
428
|
151 Here, you'd change @file{/my/path/to/package/binaries} to be the path
|
|
|
152 to your local package binaries. Next, restart XEmacs, and you're ready
|
|
|
153 to go (advanced users can just re-evaluate the sexp).
|
|
|
154
|
|
|
155 If you are installing from a temporary, one-time directory, you can also
|
|
|
156 add these directory names to @code{package-get-remote} using:
|
|
|
157
|
|
|
158 @example
|
|
440
|
159 M-x pui-add-install-directory
|
|
428
|
160 @end example
|
|
|
161
|
|
|
162 Note, however, that any directories added using this function are not
|
|
|
163 saved; this information will be lost when you quit XEmacs.
|
|
|
164
|
|
|
165 If you're going to install over the network, you only have to insure
|
|
|
166 that EFS @ref{(EFS)} works, and that it can get outside a firewall, if
|
|
|
167 you happen to be behind one. You shouldn't have to do anything else;
|
|
|
168 XEmacs already knows where to go. However you can add your own mirrors
|
|
|
169 to this list. See @code{package-get-remote}.
|
|
|
170
|
|
|
171 The easiest way to install a package is to use the visual package
|
|
|
172 browser and installer, using the menu pick:
|
|
|
173
|
|
|
174 @example
|
|
440
|
175 Options->Manage Packages->List & Install
|
|
428
|
176 @end example
|
|
|
177 or
|
|
|
178 @example
|
|
440
|
179 Options->Manage Packages->Using Custom->Select-> ...
|
|
428
|
180 @end example
|
|
|
181
|
|
|
182 You can also access it using the keyboard:
|
|
|
183
|
|
|
184 @example
|
|
|
185 M-x pui-list-packages
|
|
|
186 @end example
|
|
|
187
|
|
|
188 The visual package browser will then display a list of all packages.
|
|
|
189 Help information will be displayed at the very bottom of the buffer; you
|
|
|
190 may have to scroll down to see it. You can also press @kbd{?} to get
|
|
|
191 the same help. From this buffer, you can tell the package status by the
|
|
|
192 character in the first column:
|
|
|
193
|
|
|
194 @table @kbd
|
|
|
195 @item -
|
|
|
196 The package has not been installed.
|
|
|
197 @item *
|
|
|
198 The package has been installed, but a newer version is available. The
|
|
|
199 current version is out-of-date.
|
|
|
200 @item +
|
|
|
201 The package has been marked for installation/update.
|
|
|
202 @end table
|
|
|
203
|
|
|
204 If there is no character in the first column, the package has been
|
|
|
205 installed and is up-to-date.
|
|
|
206
|
|
|
207 From here, you can select or unselect packages for installation using
|
|
|
208 the @key{RET} key, the @kbd{Mouse-2} button or selecting "Select" from
|
|
|
209 the (Popup) Menu.
|
|
|
210 Once you've finished selecting the packages, you can
|
|
|
211 press the @kbd{x} key (or use the menu) to actually install the
|
|
|
212 packages. Note that you will have to restart XEmacs for XEmacs to
|
|
|
213 recognize any new packages.
|
|
|
214
|
|
|
215 Key summary:
|
|
|
216
|
|
|
217 @table @kbd
|
|
|
218 @item ?
|
|
|
219 Display simple help.
|
|
|
220 @item @key{RET}
|
|
|
221 @itemx @key{Mouse-2}
|
|
|
222 Toggle between selecting and unselecting a package for installation.
|
|
|
223 @item x
|
|
|
224 Install selected packages.
|
|
|
225 @item @key{SPC}
|
|
|
226 View, in the minibuffer, additional information about the package, such
|
|
|
227 as the package date (not the build date) and the package author. Moving
|
|
|
228 the mouse over a package name will also do the same thing.
|
|
|
229 @item v
|
|
|
230 Toggle between verbose and non-verbose package display.
|
|
|
231 @item g
|
|
|
232 Refresh the package display.
|
|
|
233 @item q
|
|
|
234 Kill the package buffer.
|
|
|
235 @end table
|
|
|
236
|
|
|
237 Moving the mouse over a package will also cause additional information
|
|
|
238 about the package to be displayed in the minibuffer.
|
|
|
239
|
|
|
240 @subsection Other package installation interfaces
|
|
|
241
|
|
|
242 For an alternative package interface, you can select packages from the
|
|
|
243 customize menus, under:
|
|
|
244
|
|
|
245 @example
|
|
440
|
246 Options->Customize->Emacs->Packages-> ...
|
|
428
|
247 @end example
|
|
|
248 or
|
|
|
249 @example
|
|
440
|
250 Options->Manage Packages->Using Custom->Select-> ...
|
|
428
|
251 @end example
|
|
|
252
|
|
|
253 Set their state to on, and then do:
|
|
|
254
|
|
|
255 @example
|
|
440
|
256 Options->Manage Packages->Using Custom->Update Packages
|
|
428
|
257 @end example
|
|
|
258
|
|
|
259 This will automatically retrieve the packages you have selected from the
|
|
|
260 XEmacs ftp site or your local disk, and install them into
|
|
|
261 XEmacs. Additionally it will update any packages you already have
|
|
|
262 installed to the newest version. Note that if a package is newly
|
|
|
263 installed you will have to restart XEmacs for the change to take effect.
|
|
|
264
|
|
|
265 You can also install packages using a semi-manual interface:
|
|
|
266
|
|
|
267 @example
|
|
|
268 M-x package-get-all <return>
|
|
|
269 @end example
|
|
|
270
|
|
|
271 Enter the name of the package (e.g., @code{prog-modes}), and XEmacs
|
|
|
272 will search for the latest version (as listed in the lisp file
|
|
|
273 @file{lisp/package-get-base.el}), and install it and any packages that
|
|
|
274 it depends upon.
|
|
|
275
|
|
|
276 @subsection Manual Binary Package Installation
|
|
|
277
|
|
|
278 Pre-compiled, binary packages can be installed in either a system
|
|
|
279 package directory (this is determined when XEmacs is compiled), or in
|
|
|
280 one of the following
|
|
|
281 subdirectories of your @file{$HOME} directory:
|
|
|
282
|
|
|
283 @example
|
|
|
284 ~/.xemacs/mule-packages
|
|
|
285 ~/.xemacs/xemacs-packages
|
|
|
286 @end example
|
|
|
287
|
|
|
288 Packages in the former directory will only be found by a Mule-enabled
|
|
|
289 XEmacs.
|
|
|
290
|
|
|
291 XEmacs does not have to be running to install binary packages, although
|
|
|
292 XEmacs will not know about any newly-installed packages until you
|
|
|
293 restart XEmacs. Note, however, that installing a newer version of a
|
|
|
294 package while XEmacs is running could cause strange errors in XEmacs;
|
|
|
295 it's best to exit XEmacs before upgrading an existing package.
|
|
|
296
|
|
|
297 To install binary packages manually:
|
|
|
298
|
|
|
299 @enumerate
|
|
|
300 @item
|
|
|
301 Download the package(s) that you want to install. Each binary package
|
|
|
302 will typically be a gzip'd tarball.
|
|
|
303
|
|
|
304 @item
|
|
|
305 Decide where to install the packages: in the system package
|
|
|
306 directory, or in @file{~/.xemacs/mule-packages} or
|
|
|
307 @file{~/.xemacs/xemacs-packages}, respectively. If you want to install
|
|
|
308 the packages in the system package directory, make sure you can write
|
|
|
309 into that directory. If you want to install in your @file{$HOME}
|
|
|
310 directory, create the directory, @file{~/.xemacs/mule-packages} or
|
|
|
311 @file{~/.xemacs/xemacs-packages}, respectively.
|
|
|
312
|
|
|
313 @item
|
|
|
314 Next, @code{cd} to the directory under which you want to install the
|
|
|
315 package(s).
|
|
|
316
|
|
|
317 @item
|
|
|
318 From this directory, uncompress and extract each of the gzip'd tarballs
|
|
|
319 that you downloaded in step 1. Unix and Cygnus cygwin users will
|
|
|
320 typically do this using the commands:
|
|
|
321
|
|
|
322 @example
|
|
440
|
323 gunzip < package.tar.gz | tar xvf -
|
|
428
|
324 @end example
|
|
|
325
|
|
|
326 Above, replace @file{package.tar.gz} with the filename of the
|
|
|
327 package that you downloaded in step 1.
|
|
|
328
|
|
|
329 Of course, if you use GNU @code{tar}, you could also use:
|
|
|
330
|
|
|
331 @example
|
|
440
|
332 tar xvzf package.tar.gz
|
|
428
|
333 @end example
|
|
|
334
|
|
|
335 @comment What about native MS Windows users???
|
|
|
336
|
|
|
337 @item
|
|
|
338 That's it. Quit and restart XEmacs to get it to recognize any new or
|
|
|
339 changed packages.
|
|
|
340
|
|
|
341 @end enumerate
|
|
|
342
|
|
448
|
343 @node Building Packages, Creating Packages, Using Packages, Packages
|
|
428
|
344 @comment node-name, next, previous, up
|
|
|
345
|
|
|
346 Source packages are available from the @file{packages/source-packages}
|
|
|
347 subdirectory of your favorite XEmacs distribution site. Alternatively,
|
|
|
348 they are available via CVS from @file{cvs.xemacs.org}. Look at
|
|
|
349 @file{http://cvs.xemacs.org} for instructions.
|
|
|
350
|
|
|
351 @subsection Prerequisites for Building Source Packages
|
|
|
352
|
|
|
353 You must have GNU @code{cp}, GNU @code{install} (or a BSD compatible
|
|
|
354 @code{install} program) GNU @code{make} (3.75 or later preferred),
|
|
|
355 @code{makeinfo} (1.68 from @code{texinfo-3.11} or later required), GNU
|
|
|
356 @code{tar} and XEmacs 21.0. The source packages will untar into a
|
|
|
357 correct directory structure. At the top level you must have
|
|
|
358 @file{XEmacs.rules} and @file{package-compile.el}. These files are
|
|
|
359 available from the XEmacs FTP site from the same place you obtained your
|
|
|
360 source package distributions.
|
|
|
361
|
|
|
362 @subsection What You Can Do With Source Packages
|
|
|
363
|
|
|
364 NB: A global build operation doesn't exist yet as of 13 January 1998.
|
|
|
365
|
|
|
366 Source packages are most useful for creating XEmacs package tarballs
|
|
|
367 for installation into your own XEmacs installations or for
|
|
|
368 distributing to others.
|
|
|
369
|
|
|
370 Supported operations from @file{make} are:
|
|
|
371
|
|
|
372 @table @code
|
|
|
373 @item clean
|
|
|
374 Remove all built files except @file{auto-autoloads.el} and @file{custom-load.el}.
|
|
|
375
|
|
|
376 @item distclean
|
|
|
377 Remove XEmacs backups as well as the files deleted by @code{make clean}.
|
|
|
378
|
|
|
379 @item all
|
|
|
380 Bytecompile all files, build and bytecompile byproduct files like
|
|
|
381 @file{auto-autoloads.el} and @file{custom-load.el}. Create info version
|
|
|
382 of TeXinfo documentation if present.
|
|
|
383
|
|
|
384 @item srckit
|
|
448
|
385 Usually aliased to @code{srckit-std}. This does a @code{make
|
|
428
|
386 distclean} and creates a package source tarball in the staging
|
|
|
387 directory. This is generally only of use for package maintainers.
|
|
|
388
|
|
|
389 @item binkit
|
|
|
390 May be aliased to @code{binkit-sourceonly}, @code{binkit-sourceinfo},
|
|
|
391 @code{binkit-sourcedata}, or
|
|
|
392 @code{binkit-sourcedatainfo}. @code{sourceonly} indicates there is
|
|
|
393 nothing to install in a data directory or info directory.
|
|
|
394 @code{sourceinfo} indicates that source and info files are to be
|
|
|
395 installed. @code{sourcedata} indicates that source and etc (data) files
|
|
|
396 are to be installed. @code{sourcedatainfo} indicates source, etc
|
|
|
397 (data), and info files are to be installed. A few packages have needs
|
|
|
398 beyond the basic templates so this is not yet complete.
|
|
|
399
|
|
|
400 @item dist
|
|
|
401 Runs the rules @code{srckit} followed by @code{binkit}. This is
|
|
|
402 primarily of use by XEmacs maintainers producing files for distribution.
|
|
|
403
|
|
|
404 @end table
|
|
444
|
405
|
|
448
|
406 @node Creating Packages, Available Packages, Building Packages, Packages
|
|
|
407 @comment node-name, next, previous, up
|
|
|
408
|
|
|
409 Creating a package from an existing Lisp library is not very difficult.
|
|
|
410
|
|
|
411 In addition to the Lisp libraries themselves, you need a
|
|
|
412 @file{package-info.in} file and a simple @file{Makefile}. The rest is
|
|
|
413 done by @file{XEmacs.rules}, part of the packaging system
|
|
|
414 infrastructure.
|
|
|
415
|
|
|
416 @file{package-info.in} contains a single Lisp form like this:
|
|
|
417
|
|
|
418 @example
|
|
|
419 (name ; your package's name
|
|
|
420 (standards-version 1.1
|
|
|
421 version VERSION
|
|
|
422 author-version AUTHOR_VERSION
|
|
|
423 date DATE
|
|
|
424 build-date BUILD_DATE
|
|
|
425 maintainer MAINTAINER
|
|
|
426 distribution xemacs ; change to "mule" if MULE is needed
|
|
|
427 priority high
|
|
|
428 category CATEGORY
|
|
|
429 dump nil
|
|
|
430 description "description" ; a one-line description string
|
|
|
431 filename FILENAME
|
|
|
432 md5sum MD5SUM
|
|
|
433 size SIZE
|
|
|
434 provides (feature1 feature2) ; one for every `provides' form
|
|
|
435 requires (REQUIRES)
|
|
|
436 type regular
|
|
|
437 ))
|
|
|
438 @end example
|
|
|
439
|
|
|
440 You must fill in the four commented lines. The value of @code{name} is
|
|
|
441 the name of your package as an unquoted symbol. Normally it is the name
|
|
|
442 of the main Lisp file or principal feature provided. The allowed values
|
|
|
443 for distribution are @code{xemacs} and @code{mule}. Write them as
|
|
|
444 unquoted symbols. The @code{description} is a quoted Lisp string; use
|
|
|
445 the usual conventions. The value for @code{provides} is a list of
|
|
|
446 feature symbols (written unquoted). All of the features provided by
|
|
|
447 libraries in your package should be elements of this list. Implementing
|
|
|
448 an automatic method for generating the @file{provides} line is
|
|
|
449 desirable, but as yet undone.
|
|
|
450
|
|
|
451 The variables in upper-case are references to variables set in the
|
|
|
452 @file{Makefile} or automatically generated. Do not change them; they
|
|
|
453 are automatically filled in by the build process.
|
|
|
454
|
|
|
455 The remaining lines refer to implementation constants
|
|
|
456 (@code{standards-version}), or features that are unimplemented or have
|
|
|
457 been removed (@code{priority} and @code{dump}). The @code{type} line is
|
|
|
458 not normally relevant to external maintainers; the alternate value is
|
|
|
459 @code{single-file}, which refers to packages consed up out of a number
|
|
|
460 of single-file libraries that are more or less thematically related. An
|
|
|
461 example is @code{prog-modes}. Single-file packages are basically for
|
|
|
462 administrative convenience, and new packages should generally be created
|
|
|
463 as regular packages.
|
|
|
464
|
|
|
465 The @file{Makefile} is quite stylized. The idea is similar to an
|
|
|
466 @file{Imakefile} or an @code{automake} file: the complexity is hidden in
|
|
|
467 generic rules files, in this case the @file{XEmacs.rules} include file
|
|
|
468 in the top directory of the packages hierarchy. Although a number of
|
|
|
469 facilities are available for complex libraries, most simple packages'
|
|
|
470 @file{Makefile}s contain a copyright notice, a few variable definitions,
|
|
|
471 an include for @file{XEmacs.rules}, and a couple of standard targets.
|
|
|
472
|
|
|
473 The first few @code{make} variables defined are @code{VERSION},
|
|
|
474 @code{AUTHOR_VERSION}, @code{MAINTAINER}, @code{PACKAGE},
|
|
|
475 @code{PKG_TYPE}, @code{REQUIRES}, and @code{CATEGORY}. All but one were
|
|
|
476 described in the description of @file{package-info.in}. The last is an
|
|
|
477 admistrative grouping. Current categories include @code{comm},
|
|
|
478 @code{games}, @code{libs}, @code{mule}, @code{oa}, @code{os},
|
|
|
479 @code{prog}, and @code{wp}. @ref{Available Packages}, for a list of
|
|
|
480 categories.
|
|
|
481
|
|
|
482 Next, define the variable @code{ELCS}. This contains the list of the
|
|
|
483 byte-compiled Lisp files used by the package. These files and their
|
|
|
484 @file{.el} versions will be included in the binary package. If there
|
|
|
485 are other files (such as extra Lisp sources or an upstream
|
|
|
486 @file{Makefile}) that are normally placed in the installed Lisp
|
|
|
487 directory, but not byte-compiled, they can be listed as the value of
|
|
|
488 @code{EXTRA_SOURCES}.
|
|
|
489
|
|
|
490 The include is simply
|
|
|
491 @example
|
|
|
492 include ../../XEmacs.rules
|
|
|
493 @end example
|
|
|
494
|
|
|
495 The standard targets follow. These are
|
|
|
496
|
|
|
497 @example
|
|
|
498 all:: $(ELCS) auto-autoloads.elc
|
|
|
499
|
|
|
500 srckit: srckit-alias
|
|
|
501
|
|
|
502 binkit: binkit-alias
|
|
|
503 @end example
|
|
|
504
|
|
|
505 Other targets (such as Texinfo sources) may need to be added as
|
|
|
506 dependencies for the @code{all} target. Dependencies for @code{srckit}
|
|
|
507 and @code{binkit} (that is, values for @var{srckit-alias} and
|
|
|
508 @var{binkit-alias}) are defined in @file{XEmacs.rules}. The most useful
|
|
|
509 of these values are given in the following table.
|
|
|
510
|
|
|
511 @table @var
|
|
|
512 @item srckit-alias
|
|
|
513 Usually set to @code{srckit-std}.
|
|
|
514
|
|
|
515 @item binkit-alias
|
|
|
516 May be set to @code{binkit-sourceonly}, @code{binkit-sourceinfo},
|
|
|
517 @code{binkit-sourcedata}, or
|
|
|
518 @code{binkit-sourcedatainfo}. @code{sourceonly} indicates there is
|
|
|
519 nothing to install in a data directory or info directory.
|
|
|
520 @code{sourceinfo} indicates that source and info files are to be
|
|
|
521 installed. @code{sourcedata} indicates that source and etc (data) files
|
|
|
522 are to be installed. @code{sourcedatainfo} indicates source, etc
|
|
|
523 (data), and info files are to be installed.
|
|
|
524 @end table
|
|
|
525
|
|
|
526 Data files include things like pixmaps for a package-specific toolbar,
|
|
|
527 and are normally installed in @file{etc/@var{PACKAGE_NAME}}. A few
|
|
|
528 packages have needs beyond the basic templates. See @file{XEmacs.rules}
|
|
|
529 or a future revision of this manual for details.
|
|
|
530
|
|
|
531 @node Available Packages, , Creating Packages, Packages
|
|
444
|
532 @comment node-name, next, previous, up
|
|
|
533
|
|
|
534 This section is surely out-of-date. If you're sure that XEmacs is
|
|
|
535 able to do something, but your installed XEmacs won't do it for you,
|
|
|
536 it's probably in a package. If you can't find it in this section,
|
|
|
537 that's a bug---please report it. It is very hard to keep this section
|
|
|
538 up-to-date; your reports, comments, and questions will help a lot.
|
|
|
539
|
|
|
540 This data is up-to-date as of 10 February 1999. (Ouch! I told you!)
|
|
|
541
|
|
|
542 @subsection Library Packages (libs)
|
|
|
543
|
|
|
544 These packages are required to build and support most of the rest of
|
|
|
545 XEmacs. By design, xemacs-base is a `regular' package. Use restraint
|
|
|
546 when adding new files there as it is required by almost everything.
|
|
|
547
|
|
|
548 @table @file
|
|
|
549 @item Sun
|
|
|
550 Support for Sparcworks.
|
|
|
551
|
|
|
552 @item apel
|
|
|
553 A Portable Emacs Library. Used by XEmacs MIME support.
|
|
|
554
|
|
|
555 @item edebug
|
|
|
556 A Lisp debugger.
|
|
|
557
|
|
|
558 @item dired
|
|
|
559 The DIRectory EDitor is for manipulating, and running commands on
|
|
|
560 files in a directory.
|
|
|
561
|
|
|
562 @item efs
|
|
|
563 Treat files on remote systems the same as local files.
|
|
|
564
|
|
|
565 @item mail-lib
|
|
|
566 Fundamental lisp files for providing email support.
|
|
|
567
|
|
|
568 @item tooltalk
|
|
|
569 Support for building with Tooltalk.
|
|
|
570
|
|
|
571 @item xemacs-base
|
|
|
572 Fundamental XEmacs support. Install this unless you wish a totally
|
|
|
573 naked XEmacs.
|
|
|
574
|
|
|
575 @item xemacs-devel
|
|
|
576 XEmacs Lisp developer support. This package contains utilities for
|
|
|
577 supporting Lisp development. It is a single-file package so it may be
|
|
|
578 tailored.
|
|
|
579 @end table
|
|
|
580
|
|
|
581 @subsection Communications Packages (comm)
|
|
|
582
|
|
|
583 These packages provide support for various communications, primarily
|
|
|
584 email and usenet.
|
|
|
585
|
|
|
586 @table @file
|
|
|
587 @item footnote
|
|
|
588 Footnoting in mail message editing modes.
|
|
|
589
|
|
|
590 @item gnats
|
|
|
591 XEmacs bug reports.
|
|
|
592
|
|
|
593 @item gnus
|
|
|
594 The Gnus Newsreader and Mailreader.
|
|
|
595
|
|
|
596 @item mailcrypt
|
|
|
597 Support for messaging encryption with PGP.
|
|
|
598
|
|
|
599 @item mh-e
|
|
|
600 Front end support for MH.
|
|
|
601
|
|
|
602 @item net-utils
|
|
|
603 Miscellaneous Networking Utilities. This is a single-file package and
|
|
|
604 files may be deleted at will.
|
|
|
605
|
|
|
606 @item ph
|
|
|
607 Emacs implementation of the ph client to CCSO/qi directory servers.
|
|
|
608
|
|
|
609 @item rmail
|
|
|
610 An obsolete Emacs mailer. If you do not already use it don't start.
|
|
|
611
|
|
|
612 @item supercite
|
|
|
613 An Emacs citation tool. Useful with all Emacs Mailers and Newsreaders.
|
|
|
614
|
|
|
615 @item tm
|
|
|
616 Emacs MIME support.
|
|
|
617
|
|
|
618 @item vm
|
|
|
619 An Emacs mailer.
|
|
|
620
|
|
|
621 @item w3
|
|
|
622 A Web browser.
|
|
|
623 @end table
|
|
|
624
|
|
|
625 @subsection Games and Amusements (games)
|
|
|
626
|
|
|
627 @table @file
|
|
|
628 @item cookie
|
|
|
629 Spook and Yow (Zippy quotes).
|
|
|
630
|
|
|
631 @item games
|
|
|
632 Tetris, Sokoban, and Snake.
|
|
|
633
|
|
|
634 @item mine
|
|
|
635 Minehunt.
|
|
|
636
|
|
|
637 @item misc-games
|
|
|
638 Other amusements and diversions.
|
|
|
639 @end table
|
|
|
640
|
|
|
641 @subsection Mule Support (mule)
|
|
|
642
|
|
|
643 @table @file
|
|
|
644 @item egg-its
|
|
|
645 Wnn (4.2 and 6) support. SJ3 support. Must be installed prior to
|
|
|
646 XEmacs build.
|
|
|
647
|
|
|
648 @item leim
|
|
|
649 Quail. Used for everything other than English and Japanese.
|
|
|
650
|
|
|
651 @item locale
|
|
|
652 Used for localized menubars (French and Japanese) and localized splash
|
|
|
653 screens (Japanese).
|
|
|
654
|
|
|
655 @item mule-base
|
|
|
656 Basic Mule support. Must be installed prior to building with Mule.
|
|
|
657
|
|
|
658 @item skk
|
|
|
659 Another Japanese Language Input Method. Can be used without a
|
|
|
660 separate process running as a dictionary server.
|
|
|
661 @end table
|
|
|
662
|
|
|
663 @subsection Productivity Packages (oa)
|
|
|
664
|
|
|
665 @table @file
|
|
|
666 @item calendar
|
|
|
667 Calendar and diary support.
|
|
|
668
|
|
|
669 @item edit-utils
|
|
|
670 Single file lisp packages for various XEmacs goodies. Load this and
|
|
|
671 weed out the junk you don't want.
|
|
|
672
|
|
|
673 @item forms
|
|
|
674 Forms editing support (obsolete, use the builtin Widget instead).
|
|
|
675
|
|
|
676 @item frame-icon
|
|
|
677 Provide a WM icon based on major mode.
|
|
|
678
|
|
|
679 @item hm--html-menus
|
|
|
680 HTML editing.
|
|
|
681
|
|
|
682 @item ispell
|
|
|
683 Spell-checking with ispell.
|
|
|
684
|
|
|
685 @item pc
|
|
|
686 PC style interface emulation.
|
|
|
687
|
|
|
688 @item psgml
|
|
|
689 Validated HTML/SGML editing.
|
|
|
690
|
|
|
691 @item sgml
|
|
|
692 SGML/Linuxdoc-SGML editing.
|
|
|
693
|
|
|
694 @item slider
|
|
|
695 User interface tool.
|
|
|
696
|
|
|
697 @item speedbar
|
|
|
698 ??? Document me.
|
|
|
699
|
|
|
700 @item strokes
|
|
|
701 Mouse enhancement utility.
|
|
|
702
|
|
|
703 @item text-modes
|
|
|
704 Various single file lisp packages for editing text files.
|
|
|
705
|
|
|
706 @item time
|
|
|
707 Display time & date on the modeline.
|
|
|
708 @end table
|
|
|
709
|
|
|
710 @subsection Operating System Utilities (os)
|
|
|
711
|
|
|
712 @table @file
|
|
|
713 @item eterm
|
|
|
714 Terminal emulator.
|
|
|
715
|
|
|
716 @item igrep
|
|
|
717 Enhanced front-end for Grep.
|
|
|
718
|
|
|
719 @item ilisp
|
|
|
720 Front-end for Inferior Lisp.
|
|
|
721
|
|
|
722 @item os-utils
|
|
|
723 Miscellaneous single-file O/S utilities, for printing, archiving,
|
|
|
724 compression, remote shells, etc.
|
|
|
725
|
|
|
726 @item view-process
|
|
|
727 A Unix process browsing tool.
|
|
|
728 @end table
|
|
|
729
|
|
|
730 @subsection Program Editing Support (prog)
|
|
|
731
|
|
|
732 @table @file
|
|
|
733 @item ada
|
|
|
734 Ada language support.
|
|
|
735
|
|
|
736 @item c-support
|
|
|
737 Basic single-file add-ons for editing C code.
|
|
|
738
|
|
|
739 @item cc-mode
|
|
|
740 C, C++ and Java language support.
|
|
|
741
|
|
|
742 @item debug
|
|
|
743 GUD, gdb, dbx debugging support.
|
|
|
744
|
|
|
745 @item ediff
|
|
|
746 Interface over patch.
|
|
|
747
|
|
|
748 @item emerge
|
|
|
749 Another interface over patch.
|
|
|
750
|
|
|
751 @item pcl-cvs
|
|
|
752 CVS frontend.
|
|
|
753
|
|
|
754 @item prog-modes
|
|
446
|
755 Miscellaneous Lisp libraries for various programming languages.
|
|
444
|
756
|
|
|
757 @item scheme
|
|
|
758 Front-end support for Inferior Scheme.
|
|
|
759
|
|
|
760 @item sh-script
|
|
|
761 Support for editing shell scripts.
|
|
|
762
|
|
|
763 @item vc
|
|
446
|
764 Version control for free systems.
|
|
444
|
765
|
|
|
766 @item vc-cc
|
|
446
|
767 Version control for ClearCase.
|
|
444
|
768
|
|
|
769 @item vhdl
|
|
|
770 Support for VHDL.
|
|
|
771 @end table
|
|
|
772
|
|
|
773 @subsection Word Processing (wp)
|
|
|
774
|
|
|
775 @table @file
|
|
|
776 @item auctex
|
|
|
777 Basic TeX/LaTeX support.
|
|
|
778
|
|
|
779 @item crisp
|
|
|
780 Crisp/Brief emulation.
|
|
|
781
|
|
|
782 @item edt
|
|
|
783 DEC EDIT/EDT emulation.
|
|
|
784
|
|
|
785 @item texinfo
|
|
|
786 XEmacs TeXinfo support.
|
|
|
787
|
|
|
788 @item textools
|
|
|
789 Single-file TeX support.
|
|
|
790
|
|
|
791 @item tpu
|
|
|
792 DEC EDIT/TPU support.
|
|
|
793
|
|
|
794 @item viper
|
|
|
795 VI emulation support.
|
|
|
796 @end table
|
|
|
797
|
