comparison etc/BETA @ 209:41ff10fd062f r20-4b3

Import from CVS: tag r20-4b3
author cvs
date Mon, 13 Aug 2007 10:04:58 +0200
parents 850242ba4a81
children 2c611d1463a6
comparison
equal deleted inserted replaced
208:f427b8ec4379 209:41ff10fd062f
215 you will probably lose due to tab expansion. The best thing to do is 215 you will probably lose due to tab expansion. The best thing to do is
216 to use an XEmacs shell buffer to run the diff commands, or ... 216 to use an XEmacs shell buffer to run the diff commands, or ...
217 M-x cd to the appropriate directory, and issue the command `C-u M-!' from 217 M-x cd to the appropriate directory, and issue the command `C-u M-!' from
218 within XEmacs. 218 within XEmacs.
219 219
220 * XEmacs 20.3 packages 220 * XEmacs 20.4 packages
221 221
222 XEmacs 20.3 has added the concept of installable packages searched prior 222 XEmacs 20.4 has added the concept of installable packages searched prior
223 to dump time when building. 223 to dump time when building.
224 224
225 Packages are searched by default under /usr/local/lib/xemacs/packages/. 225 Packages are searched by default under /usr/local/lib/xemacs/packages/.
226 The summary message in configure will tell you where XEmacs is looking 226 The summary message in configure will tell you where XEmacs is looking
227 for them. The packages hierarchy differs from site-lisp in that you 227 for them. The packages hierarchy differs from site-lisp in that you
252 ./lisp/footnote 252 ./lisp/footnote
253 ./lisp/skk 253 ./lisp/skk
254 254
255 255
256 AUCTeX and Gnus have package tarballs in 256 AUCTeX and Gnus have package tarballs in
257 ftp://ftp.xemacs.org/pub/beta/packages-20.3/ 257 ftp://ftp.xemacs.org/pub/beta/xemacs-20.4/packages/
258 that you can simply untar in a package directory to install. 258 that you can simply untar in a package directory to install.
259 259
260 Karl Hegbloom has a set of packages in 260 Karl Hegbloom has a set of packages in
261 [sorry - reference has been lost] 261 [sorry - reference has been lost]
262 that work the same way. 262 that work the same way.
263 263
264 ** Packages directory on the FTP Site 264 ** Packages directory on the FTP Site
265 ===================================== 265 =====================================
266 266
267 The packages directory 267 The packages directory
268 ftp://ftp.xemacs.org/pub/xemacs/beta/packages-20.3/ 268 ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-20.4/packages/
269 269
270 is divided into subdirectory by the major type of package. 270 is divided into subdirectory by the major type of package.
271 271
272 drwxr-xr-x 2 beta-f beta-f 1024 Oct 10 00:43 binary-packages 272 drwxr-xr-x 2 beta-f beta-f 1024 Oct 10 00:43 binary-packages
273 drwxr-xr-x 2 beta-f beta-f 512 Oct 10 00:44 package-sources 273 drwxr-xr-x 2 beta-f beta-f 512 Oct 10 00:44 package-sources
292 command to install. 292 command to install.
293 293
294 ** Binary package installation (binary-packages) 294 ** Binary package installation (binary-packages)
295 ================================================ 295 ================================================
296 296
297 Prerequisite: XEmacs 20.3-beta28. 297 Prerequisite: XEmacs 20.4-b1.
298 298
299 Binary packages are complete entities that can be untarred at the top 299 Binary packages are complete entities that can be untarred at the top
300 level of an XEmacs package hierarchy and work at runtime. To install files 300 level of an XEmacs package hierarchy and work at runtime. To install files
301 in this directory, run the command `M-x package-admin-add-binary-package' 301 in this directory, run the command `M-x package-admin-add-binary-package'
302 and fill in appropriate values to the prompts. 302 and fill in appropriate values to the prompts.
303 303
304 ** Single file package installation 304 ** Single file package installation
305 =================================== 305 ===================================
306 306
307 Prerequisite: XEmacs 20.3-beta28. 307 Prerequisite: XEmacs 20.4-b1.
308 308
309 These are single file, self-contained lisp packages that don't need a 309 These are single file, self-contained lisp packages that don't need a
310 separate directory. To install something from this directory, run 310 separate directory. To install something from this directory, run
311 the command `M-x package-admin-add-single-file-package' and fill in the 311 the command `M-x package-admin-add-single-file-package' and fill in the
312 prompts. 312 prompts.