Mercurial > hg > xemacs-beta

comparison etc/BETA @ 253:157b30c96d03 r20-5b25

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-5b25
author cvs
date Mon, 13 Aug 2007 10:20:27 +0200
parents f220cc83d72e
children 11cf20601dec
comparison
equal deleted inserted replaced
252:afb15df44434 253:157b30c96d03
282 282
283 is divided into subdirectory by the major type of package. 283 is divided into subdirectory by the major type of package.
284 284
285 drwxr-xr-x 2 beta-f beta-f 1024 Oct 10 00:43 binary-packages 285 drwxr-xr-x 2 beta-f beta-f 1024 Oct 10 00:43 binary-packages
286 drwxr-xr-x 2 beta-f beta-f 512 Oct 10 00:44 package-sources 286 drwxr-xr-x 2 beta-f beta-f 512 Oct 10 00:44 package-sources
287 drwxr-xr-x 2 beta-f beta-f 512 Oct 9 23:08 single-file-packages
288 drwxr-xr-x 2 beta-f beta-f 512 Oct 10 00:44 utils 287 drwxr-xr-x 2 beta-f beta-f 512 Oct 10 00:44 utils
289 288
290 ** Support Utilities (utils) 289 ** Support Utilities (utils)
291 ============================ 290 ============================
292 291
294 have not had yet gotten XEmacs package integration. The script `xpackage.sh' 293 have not had yet gotten XEmacs package integration. The script `xpackage.sh'
295 is used with Quassia Gnus. Edit the appropriate variables at the top of 294 is used with Quassia Gnus. Edit the appropriate variables at the top of
296 the script to reflect the local configuration and run it in the top level 295 the script to reflect the local configuration and run it in the top level
297 directory of a Quassia Gnus source tree to install an update to Quassia Gnus. 296 directory of a Quassia Gnus source tree to install an update to Quassia Gnus.
298 297
299 ** Source Installable Packages (package-sources)
300 ================================================
301
302 This directory contains tarballs of Lisp packages that contain full support
303 for installing as an XEmacs package. To install them, one should untar
304 them to someplace convenient (like /var/tmp), and issue the appropriate make
305 command to install.
306
307 ** Binary package installation (binary-packages) 298 ** Binary package installation (binary-packages)
308 ================================================ 299 ================================================
309 300
310 Prerequisite: XEmacs 20.5-b1. 301 Prerequisite: XEmacs 20.5-b1.
311 302
312 Binary packages are complete entities that can be untarred at the top 303 Binary packages are complete entities that can be untarred at the top
313 level of an XEmacs package hierarchy and work at runtime. To install files 304 level of an XEmacs package hierarchy and work at runtime. To install files
314 in this directory, run the command `M-x package-admin-add-binary-package' 305 in this directory, run the command `M-x package-admin-add-binary-package'
315 and fill in appropriate values to the prompts. 306 and fill in appropriate values to the prompts.
316
317 ** Single file package installation
318 ===================================
319
320 Prerequisite: XEmacs 20.5-b1.
321
322 These are single file, self-contained lisp packages that don't need a
323 separate directory. To install something from this directory, run
324 the command `M-x package-admin-add-single-file-package' and fill in the
325 prompts.
326 307
327 ** Manual procedures for package management 308 ** Manual procedures for package management
328 =========================================== 309 ===========================================
329 310
330 Prerequisite: XEmacs 20.5 311 Prerequisite: XEmacs 20.5
344 325
345 To bytecompile both of these files the command is: 326 To bytecompile both of these files the command is:
346 327
347 xemacs-20.5 -vanilla -batch -f batch-byte-compile \ 328 xemacs-20.5 -vanilla -batch -f batch-byte-compile \
348 lisp-utils/auto-autoloads.el lisp-utils/custom-laod.el 329 lisp-utils/auto-autoloads.el lisp-utils/custom-laod.el
330
331 ** Building XEmacs and XEmacs packages from scratch
332 ===================================================
333
334 To build everything completely from scratch (not a high priority as a
335 design goal), the following procedure should work. (I don't recommend
336 building this way).
337
338 *** Phase 1 -- Get a minimal XEmacs binary with mule to build the package
339 lisp with.
340
341 **** Grab a mule-base tarball and install it into a newly created package
342 directory.
343
344 **** Configure XEmacs with mule and a package-path including the
345 directory created above.
346
347 **** Do a `make dist' to build an XEmacs binary.
348
349 *** Phase 2 -- Build and install the package lisp.
350
351 **** Modify XEmacs.rules for local paths and the XEmacs binary created in
352 Phase 1.
353
354 **** Do a make from the top level package lisp source directory.[1]
355
356 ***** There are two build glitches at this time. You must `make
357 auto-autoloads.el' manually in comm/tm before starting if you have
358 done a `make distclean'. This should be unnecessary after a fresh
359 cvs checkout.
360
361 ***** You must go back and rebuild the strokes package after the main
362 build is complete.
363
364 **** Do `make bindist's on all the packages you wish to install and
365 remove the byproduct .tar.gz's.
366
367 *** Phase 3 -- Redump XEmacs with the packages that require dump time
368 support (like egg-its, VM, etc.) and install it.
369
370 **** Reconfigure without Mule if you don't wish a Mule-ish XEmacs, and
371 rebuild XEmacs.
372
373 - or -
374
375 **** rm lib-src/DOC src/xemacs; make
376
377 **** Install or run in-place.
378
379 Note that this is in essence what `make all-elc' has always done.