comparison etc/bundled-packages/README @ 4354:232d873b9705

Add support for installing bundled patches.
author Stephen J. Turnbull <stephen@xemacs.org>
date Sun, 23 Dec 2007 20:32:16 -0800
parents
children 146742e30f05
comparison
equal deleted inserted replaced
4353:4143b78d0df0 4354:232d873b9705
1 Package distributions may be placed in this directory.
2 If present and a package-path is configured, packages can be installed
3 using the top-level makefile.
4
5 To configure the package path, use the --with-late-packages option to
6 configure, which specifies the path to the directory containing the
7 xemacs-packages and mule-packages hierarchies to install.
8
9 To find out if a distribution includes bundled packages, type
10
11 make check-available-packages
12
13 There are three Make targets that may be available depending on the package
14 sets supplied.
15
16 make install-bootstrap-packages
17 Install a selected set of packages sufficient to support
18 downloading and installing packages via the M-x list-packages
19 interface. Chose this if you want to be able to install the
20 latest version of each package immediately.
21
22 make install-nomule-packages
23 Install the full distribution of packages that do not require a
24 Mule-enabled XEmacs. Choose this package if you don't have a
25 Mule-enabled XEmacs and want the convenience of a single-command
26 installation. You can add or update packages via M-x list-packages
27 at any time.
28
29 make install-all-packages
30 Install the full distribution of packages, including those requiring
31 a Mule-enabled XEmacs. Choose this package if you have a Mule-
32 enabled XEmacs and want the convenience of a single-command
33 installation. You can add or update packages via M-x list-packages
34 at any time.
35
36 DISTRIBUTOR'S NOTE: you may choose what packages you wish to include in
37 bootstrap.tar.gz, but to make list-packages work you need to include at
38 least xemacs-base, dired, and efs. The tarball should unpack directly as
39 an xemacs-packages tree (and optionaly, a mule-packages tree. Also, if
40 either of xemacs-sumo.tar.gz or xemacs-mule-sumo.tar.gz is provided, the
41 other should be as well.
42
43 If packages are not available with the distribution, you can get them at
44
45 ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz
46 ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz
47 http://turnbull.sk.tsukuba.ac.jp/Tools/XEmacs/bootstrap.tar.gz
48
49 and place them in the same directory as this file. You can also make your
50 own bootstrap.tar.gz by creating a directory xemacs-packages, then
51 untarring the packages of your choice into that directory, and tarring the
52 whole thing up with "tar czf bootstrap.tar.gz xemacs-packages". (If you
53 wish to include mule-packages, you should place them in mule-packages as
54 a sibling of xemacs-packages.)
55
56 This facility currently does not support installations which configure
57 the --with-early-packages, --with-late-packages, or --with-last-packages
58 options.
59
60 This facility currently will not overwrite an existing package
61 installation, not even if a whole hierarchy (usually the mule-packages)
62 is missing. In particular, you cannot use this feature to add the
63 mule-packages to a package installation which lacks them, even if the
64 hierarchy is missing, or the xemacs-packages hierarchy was installed
65 this way. Nor can you "upgrade" a bootstrap installation to a full
66 installation. If you wish to do any of these things you will need to
67 remove the existing hierarchies.
68