Mercurial > hg > xemacs-beta
comparison README.packages @ 359:8e84bee8ddd0 r21-1-9
Import from CVS: tag r21-1-9
author | cvs |
---|---|
date | Mon, 13 Aug 2007 10:57:55 +0200 |
parents | 182f72e8cd0d |
children | a4f53d9b3154 |
comparison
equal
deleted
inserted
replaced
358:fed6e0f6a03a | 359:8e84bee8ddd0 |
---|---|
7 | 7 |
8 Real Real Quickstart FAQ | 8 Real Real Quickstart FAQ |
9 ------------------------ | 9 ------------------------ |
10 | 10 |
11 Q. Do I need to have the packages to compile XEmacs? | 11 Q. Do I need to have the packages to compile XEmacs? |
12 A. No. | 12 A. No, XEmacs will build and install just fine without any packages |
13 installed. However, only the most basic editing functions will be | |
14 available with no packages installed, so installing packages is an | |
15 essential part of making your installed XEmacs _useful_. | |
13 | 16 |
14 Q. I really liked the old way that packages were bundled and do not | 17 Q. I really liked the old way that packages were bundled and do not |
15 want to mess with packages at all. | 18 want to mess with packages at all. |
16 A. You can grab all the packages at once like you used to with old | 19 A. You can grab all the packages at once like you used to with old |
17 XEmacs versions, skip to the 'Sumo Tarball' section below. | 20 XEmacs versions, skip to the 'Sumo Tarball' section below. |
57 | 60 |
58 Where to get the packages | 61 Where to get the packages |
59 ------------------------- | 62 ------------------------- |
60 | 63 |
61 Packages are available from ftp://ftp.xemacs.org/pub/xemacs/packages | 64 Packages are available from ftp://ftp.xemacs.org/pub/xemacs/packages |
62 and its mirror. | 65 and its mirrors. |
63 | 66 |
64 How to install the packages | 67 How to install the packages |
65 --------------------------- | 68 --------------------------- |
66 | 69 |
67 1. All at once, using the 'Sumo Tarball'. | 70 1. All at once, using the 'Sumo Tarball'. |
70 | 73 |
71 The Sumo Tarball | 74 The Sumo Tarball |
72 ---------------- | 75 ---------------- |
73 | 76 |
74 Those with little time, cheap connections and plenty of disk space can | 77 Those with little time, cheap connections and plenty of disk space can |
75 install all packages at once using the sumo tarballs. | 78 install all the packages at once using the sumo tarballs. |
76 Download the file | 79 Download the file |
77 | 80 |
78 xemacs-sumo-<date>.tar.gz | 81 xemacs-sumo.tar.gz |
79 | 82 |
80 For an XEmacs compiled with Mule you also need | 83 For an XEmacs compiled with Mule you also need |
81 | 84 |
82 xemacs-mule-sumo-<date>.tar.gz | 85 xemacs-mule-sumo.tar.gz |
83 | 86 |
84 N.B. They are called 'Sumo Tarballs' for good reason. They are | 87 N.B. They are called 'Sumo Tarballs' for good reason. They are |
85 currently about 15MB and 2.3MB (gzipped) respectively. | 88 currently about 15MB and 2.3MB (gzipped) respectively. |
86 | 89 |
87 Install them by | 90 Install them by |
129 | 132 |
130 and optionally: | 133 and optionally: |
131 | 134 |
132 mailcrypt - If you have PGP installed and want to verify the | 135 mailcrypt - If you have PGP installed and want to verify the |
133 signature of the index file. | 136 signature of the index file. |
134 mule-base - Needed if you want to run XEmacs with MULE with a | 137 mule-base - Needed if you want to use XEmacs with MULE. |
135 non-English language environment. | |
136 | 138 |
137 After installing these by hand, you can start XEmacs. (It is a good | 139 After installing these by hand, you can start XEmacs. (It is a good |
138 idea to use 'xemacs -vanilla' here as your startup files might need | 140 idea to use 'xemacs -vanilla' here as your startup files might need |
139 things now moved to packages.) | 141 things now moved to packages.) |
140 | 142 |
199 Finding the Right Packages | 201 Finding the Right Packages |
200 -------------------------- | 202 -------------------------- |
201 | 203 |
202 If you want to find out which package contains the functionality you | 204 If you want to find out which package contains the functionality you |
203 are looking for, use M-x package-get-package-provider, and give it a | 205 are looking for, use M-x package-get-package-provider, and give it a |
204 symbol that is likely to be in that package. eg, if some code you | 206 symbol that is likely to be in that package. For example, if some |
205 want to use has a (require 'thingatpt) in it, try doing | 207 code you want to use has a (require 'thingatpt) in it, try doing |
206 M-x package-get-package-provider RET thingatpt , which will return | 208 M-x package-get-package-provider RET thingatpt , which will return |
207 something like: (fsf-compat "1.06"). | 209 something like: (fsf-compat "1.06"). |
208 | 210 |
209 Upgrading/Removing Packages | 211 Upgrading/Removing Packages |
210 --------------------------- | 212 --------------------------- |
211 | 213 |
212 As the exact files and their locations contained in a package may | 214 As the exact files and their locations contained in a package may |
213 change it is recommend to remove a package first before installing a | 215 change it is recommended to remove a package first before installing a |
214 new version. In order to facilitate removal each package contains an | 216 new version. In order to facilitate removal each package contains an |
215 pgkinfo/MANIFEST.pkgname file which list all the files belong to the | 217 pgkinfo/MANIFEST.pkgname file which list all the files belong to the |
216 package. M-x package-admin-delete-binary-package RET can be used to | 218 package. M-x package-admin-delete-binary-package RET can be used to |
217 remove a package using this file. | 219 remove a package using this file. |
218 | 220 |