Mercurial > hg > xemacs-beta

comparison man/xemacs/packages.texi @ 316:512e409c26a2 r21-0b56

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-0b56
author cvs
date Mon, 13 Aug 2007 10:44:46 +0200
parents 341dac730539
children 19dcec799385
comparison
equal deleted inserted replaced
315:5e87bc5b1ee4 316:512e409c26a2
128 @example 128 @example
129 (setq package-get-remote (cons (list nil "/my/path/to/package/binaries") 129 (setq package-get-remote (cons (list nil "/my/path/to/package/binaries")
130 package-get-remote)) 130 package-get-remote))
131 @end example 131 @end example
132 132
133 Here, you'd change @code{"/my/path/to/package/binaries"} to be the path 133 Here, you'd change @file{/my/path/to/package/binaries} to be the path
134 to your local package binaries. Next, restart XEmacs, and you're ready 134 to your local package binaries. Next, restart XEmacs, and you're ready
135 to go (advanced users can just re-evaluate the sexp). 135 to go (advanced users can just re-evaluate the sexp).
136
137 If you are installing from a temporary, one-time directory, you can also
138 add these directory names to @code{package-get-remote} using:
139
140 @example
141 M-x pui-add-install-directory
142 @end example
143
144 Note, however, that any directories added using this function are not
145 saved; this information will be lost when you quit XEmacs.
136 146
137 If you're going to install over the network, you only have to insure 147 If you're going to install over the network, you only have to insure
138 that EFS @ref{(EFS)} works, and that it can get outside a firewall, if 148 that EFS @ref{(EFS)} works, and that it can get outside a firewall, if
139 you happen to be behind one. You shouldn't have to do anything else; 149 you happen to be behind one. You shouldn't have to do anything else;
140 XEmacs already knows where to go. 150 XEmacs already knows where to go.
222 XEmacs ftp site or your local disk, and install them into 232 XEmacs ftp site or your local disk, and install them into
223 XEmacs. Additionally it will update any packages you already have 233 XEmacs. Additionally it will update any packages you already have
224 installed to the newest version. Note that if a package is newly 234 installed to the newest version. Note that if a package is newly
225 installed you will have to restart XEmacs for the change to take effect. 235 installed you will have to restart XEmacs for the change to take effect.
226 236
227 You can also install packages manually, using: 237 You can also install packages using a semi-manual interface:
228 238
229 @example 239 @example
230 M-x package-get-all <return> 240 M-x package-get-all <return>
231 @end example 241 @end example
232 242
233 Enter the name of the package (e.g., @code{prog-modes}), and XEmacs 243 Enter the name of the package (e.g., @code{prog-modes}), and XEmacs
234 will search for the latest version (as listed in the lisp file 244 will search for the latest version (as listed in the lisp file
235 @file{lisp/package-get-base.el}), and install it and any packages that 245 @file{lisp/package-get-base.el}), and install it and any packages that
236 it depends upon. 246 it depends upon.
247
248 @subsection Manual Binary Package Installation
249
250 Pre-compiled, binary packages can be installed in either a system
251 package directory (this is determined when XEmacs is compiled), or in a
252 subdirectory off your @file{$HOME} directory:
253
254 @example
255 ~/.xemacs/packages
256 @end example
257
258 XEmacs does not have to be running to install binary packages, although
259 XEmacs will not know about any newly-installed packages until you
260 restart XEmacs. Note, however, that installing a newer version of a
261 package while XEmacs is running could cause strange errors in XEmacs;
262 it's best to exit XEmacs before upgrading an existing package.
263
264 To install binary packages manually:
265
266 @enumerate
267 @item
268 Download the package(s) that you want to install. Each binary package
269 will typically be a gzip'd tarball.
270
271 @item
272 Decide where to install the packages: in the system package directory,
273 or in @file{~/.xemacs/packages}. If you want to install the
274 packages in the system package directory, make sure you can write into
275 that directory. If you want to install in your @file{$HOME} directory,
276 create the directory, @file{~/.xemacs/packages}.
277
278 @item
279 Next, @code{cd} to the directory under which you want to install the
280 package(s).
281
282 @item
283 From this directory, uncompress and extract each of the gzip'd tarballs
284 that you downloaded in step 1. Unix and Cygnus cygwin users will
285 typically do this using the commands:
286
287 @example
288 gunzip < package.tar.gz | tar xvf -
289 @end example
290
291 Above, replace @file{package.tar.gz} with the filename of the
292 package that you downloaded in step 1.
293
294 Of course, if you use GNU @code{tar}, you could also use:
295
296 @example
297 tar xvzf package.tar.gz
298 @end example
299
300 @comment What about native MS Windows users???
301
302 @item
303 That's it. Quit and restart XEmacs to get it to recognize any new or
304 changed packages.
305
306 @end enumerate
237 307
238 @node Building Packages, , Using Packages, Packages 308 @node Building Packages, , Using Packages, Packages
239 @comment node-name, next, previous, up 309 @comment node-name, next, previous, up
240 310
241 Source packages are available from the @file{packages/source-packages} 311 Source packages are available from the @file{packages/source-packages}