Mercurial > hg > xemacs-beta
view etc/bundled-packages/README @ 5046:d4f666cda5e6
some random fixups
-------------------- ChangeLog entries follow: --------------------
man/ChangeLog addition:
2010-02-20 Ben Wing <ben@xemacs.org>
* internals/internals.texi (Intro to Window and Frame Geometry):
Shrink diagram to fit when offset by five spaces as a result of
quoting.
src/ChangeLog addition:
2010-02-20 Ben Wing <ben@xemacs.org>
* syswindows.h:
Add table about GNU Emacs -> XEmacs Windows constants from
the internals manual.
* frame.c:
Shrink size of diagram consistent with internals manual.
* alloc.c:
* compiler.h:
* console.c:
* events.c:
* gc.c (gc_stat_start_new_gc):
* gc.c (gc_stat_resume_gc):
* gc.c (kkcc_marking):
* gc.c (gc_1):
* gc.c (gc):
* objects-tty.c:
* redisplay-msw.c:
* redisplay-msw.c (mswindows_clear_region):
* syntax.c:
* syntax.c (ST_COMMENT_STYLE):
* sysdep.c:
Fix various compiler warnings.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Sat, 20 Feb 2010 03:24:08 -0600 |
parents | 146742e30f05 |
children | fd714e8ba81e |
line wrap: on
line source
Package distributions may be placed in this directory. If present and a package-path is configured, packages can be installed using the top-level Makefile. To configure the package path, use the --with-late-packages option to configure, which specifies a single directory in which to install the xemacs-packages and mule-packages hierarchies provided. If this is null, or contains a Unix-style search path (i.e., a colon is present in the argument of the --with-late-packages option), you will have to install the packages by hand. To find out if a distribution includes bundled packages, type make check-available-packages There are three Make targets that may be available depending on the package sets supplied. make install-bootstrap-packages Install a selected set of packages sufficient to support downloading and installing packages via the M-x list-packages interface. Chose this if you want to be able to install the latest version of each package immediately. make install-nomule-packages Install the full distribution of packages that do not require a Mule-enabled XEmacs. Choose this package if you don't have a Mule-enabled XEmacs and want the convenience of a single-command installation. You can add or update packages via M-x list-packages at any time. make install-all-packages Install the full distribution of packages, including those requiring a Mule-enabled XEmacs. Choose this package if you have a Mule- enabled XEmacs and want the convenience of a single-command installation. You can add or update packages via M-x list-packages at any time. DISTRIBUTOR'S NOTE: you may choose what packages you wish to include in bootstrap.tar.gz, but to make list-packages work you need to include at least xemacs-base, dired, and efs. The tarball should unpack directly as an xemacs-packages tree (and optionaly, a mule-packages tree. Also, if either of xemacs-sumo.tar.gz or xemacs-mule-sumo.tar.gz is provided, the other should be as well. If packages are not available with the distribution, you can get them at ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz http://turnbull.sk.tsukuba.ac.jp/Tools/XEmacs/bootstrap.tar.gz and place them in the same directory as this file. You can also make your own bootstrap.tar.gz by creating a directory xemacs-packages, then untarring the packages of your choice into that directory, and tarring the whole thing up with "tar czf bootstrap.tar.gz xemacs-packages". (If you wish to include mule-packages, you should place them in mule-packages as a sibling of xemacs-packages.) This facility currently does not support installations which configure the --with-early-packages, --with-late-packages, or --with-last-packages options. This facility currently will not overwrite an existing package installation, not even if a whole hierarchy (usually the mule-packages) is missing. In particular, you cannot use this feature to add the mule-packages to a package installation which lacks them, even if the hierarchy is missing, or the xemacs-packages hierarchy was installed this way. Nor can you "upgrade" a bootstrap installation to a full installation. If you wish to do any of these things you will need to remove the existing hierarchies.