>>>"AP" == Andy Piper schrieb am Wed, 15 Jul 1998
AP> Here are my comments and additions, additions have >>>>New
AP> Stuff>>>, comments are just in straight text.
Comments on your comments/additions.
AP> Packages are also
listed on the options menu under:
AP> If you have efs installed and configured packages can be
AP> installed completely from the menubar.
We need to mention how this can be accomplished with plain M-x
> Here is an overview which packages should be dumped  with
> XEmacs and thus need to be installed before compiling XEmacs, if
> you like to use them.
AP> This is misleading (correct me if I'm wrong someone). What you
AP> are dumping are basically hooks for the package which make it
AP> possible to use the package with little configuration. There's
AP> nothing to stop you installing a package manually loading it and
AP> then using it. I'm assuming that xemacs binaries will come
AP> pre-dumped with these hooks in which case people want have to
Allright. Should I then delete the passage alltogether ? What about
the Mule-setup ? efs ? Is there somethings necessary to get this going
and should there be a passage explaining it ?
> <I think we also need a list of suggestions for people that
> to do several stuff with XEmacs, like reading/sending mail,
> programming, W3 surfing, etc. You get the idea. Yes, I know of
> etc/PACKAGES but that contains no suggestions.>
Anybody wanting to comment on this one ?
> *3. Directories ===============
contains functions that will install packages for you in
AP> the correct location, meaning that you the user do not have to
AP> worry about where they are. For information puposes:
I dislike the last sentence. Is it true that all users should start
with a naked XEmacs, downloading all packages from within XEmacs later
on ? If so, I must admit that I don't like it to be done this way.
> *4. Installing packages and XEmacs
If the following stuff intended as an add-on (i.e. >>>New Stuff) ?
AP> The easiest and most correct way to install a package is to do:
AP> M-x package-admin-add-binary-package <return>
AP> input the location of the package tarball and xemacs will do the
AP> rest for you. If you have efs installed and configured you can
AP> select package from the customize menu, set their state to on and
AP> then do:
options-> customize->update packages
This corresponds to M-x package-get-update-all, doesn't it ?
AP> This will automatically retrieve the packages you have selected
AP> from the xemacs ftp site and install them into
AP> xemacs. Additionally it will update any packages you already have
AP> installed to the newest version. Note that if a package is newly
AP> installed you will have to restart XEmacs for the change to take
AP> Alternatively you can install packages by hand using tar,
AP> although this is not recommended since
AP> package-admin-add-binary-package may perform additional steps in
AP> the future:
AP> The end goal of the efs-based package distribution is for you to
AP> be able to:
AP> 1. Download and install and xemacs binary. 2. Download and
AP> install the efs package 3. Configure efs. 4. Select packages
AP> from the options menu and install them automatically.
AP> Currently efs has some dependencies which means that you may have
AP> to install more than efs to get going. Also as noted earlier you
AP> have to currently restart XEmacs once packages have been
These dependencies of efs, and Mule probably as well, are the ones
that made me talk about "packages that should be dumped with XEmacs" -
I see that my passage is incorrect, but I think these packages that
need to be installed first-hand should be mentioned in this document.
> *5. Using Packages from Emacs Lisp
AP> I don't know what this means. I think you should delete it.
The headline may be a bit misleading. I am concerned with using M-x
package* functions and setting some of the variables. For example, I
tried to use
; 21.X introduces packages. Koblenz is my nearest mirror.
So, things like this should be explained here (or somewhere in the
info files at last).
BTW: In 21.0 \"Zhong Wei\" XEmacs Lucid and the corresponding
package-*.els I had trouble updating my packages. For example, for w3
I had 1.06 installed, but the oldest version that could be found on
was 1.07, so package-get-update-all failed complaining
that it couldn't find w3-1.06. I'm currently updating to b50 and
"CL enhances the productivity of programmers. Scheme, to me, is
manual *work*. It would make an excellent extension language for vi."
-- Lars Magne Ingebrigtsen on xemacs-beta