Mercurial > hg > xemacs-beta

view etc/bundled-packages/README @ 5015:d95c102a96d3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
cleanups for specifier font stages, from ben-unicode-internal (preparation for eliminating shadowed warnings) -------------------- ChangeLog entries follow: -------------------- src/ChangeLog addition: 2010-02-08 Ben Wing <ben@xemacs.org> * faces.c: * faces.c (face_property_matching_instance): * faces.c (ensure_face_cachel_contains_charset): * faces.h (FACE_FONT): * lisp.h: * lisp.h (enum font_specifier_matchspec_stages): * objects-msw.c: * objects-msw.c (mswindows_font_spec_matches_charset): * objects-msw.c (mswindows_find_charset_font): * objects-tty.c: * objects-tty.c (tty_font_spec_matches_charset): * objects-tty.c (tty_find_charset_font): * objects-xlike-inc.c: * objects-xlike-inc.c (XFUN): * objects-xlike-inc.c (xft_find_charset_font): * objects.c: * objects.c (font_instantiate): * objects.c (FROB): * specifier.c: * specifier.c (charset_matches_specifier_tag_set_p): * specifier.c (call_charset_predicate): * specifier.c (define_specifier_tag): * specifier.c (Fdefine_specifier_tag): * specifier.c (setup_charset_initial_specifier_tags): * specifier.c (specifier_instance_from_inst_list): * specifier.c (FROB): * specifier.c (vars_of_specifier): * specifier.h: Rename the specifier-font-matching stages in preparation for eliminating shadowed warnings, some other related fixes from ben-unicode-internal. 1. Rename raw enums: initial -> STAGE_INITIAL final -> STAGE_FINAL impossible -> NUM_MATCHSPEC_STAGES 2. Move `enum font_specifier_matchspec_stages' from specifier.h to lisp.h. 3. Whitespace changes to match coding standards. 4. Eliminate unused second argument STAGE in charset predicates that don't use it -- the code that calls the charset predicates is now smart enough to supply the right number of arguments automatically. 5. Add some long(ish) comments and authorial notices, esp. in objects.c. 6. In specifier.c, change Vcharset_tag_lists from a vector over leading bytes to a hash table over charsets. This change is unnecessary currently but doesn't hurt and will be required when we merge in Unicode-internal. 7. In specifier.c, extract out the code that calls charset predicates into a function call_charset_predicate().
author Ben Wing <ben@xemacs.org>
date Mon, 08 Feb 2010 16:51:25 -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.