Rebecca Ore <ore(a)op.net> writes:
> Do I need to recompile?
No you no not.
Could please mail the output of '(locate-library
"toolbar-fancy")' and '(locate-data-directory "toolbar-fancy")' and
the value of toolbar-mail-icon.
> I found the entry about Paths and don't see how that's relevant as
> I've been able to up-grade Gnus without recompiling.
I recommended you read it because it explains you what things like
'site-packages' mean. Here is it is.
Package Hierarchies
-------------------
Many relevant directories and files XEmacs uses are actually not
part of the core installation. They are part of any of the many
packages usually installed on top of an XEmacs installation. (*Note
Packages::.) Hence, they play a prominent role in the various paths
XEmacs sets up.
XEmacs locates packages in any of a number of package hierarchies.
Package hierarchies fall into three groups: "early", "late", and "last",
according to the relative location at which they show up in the various
XEmacs paths. Early package hierarchies are at the very front, late
ones somewhere in the middle, and last hierarchies are (you guessed it)
last.
By default, XEmacs expects an early package hierarchy in the a
subdirectory `.xemacs' of the user's home directory.
Moreover, XEmacs expects late hierarchies in the subdirectories
`site-packages', `mule-packages', and `xemacs-packages' (in that order)
of the `<root>/lib/xemacs' subdirectory of one of the installation
hierarchies. (If you run in-place, these are direct subdirectories of
the build directory.) Furthermore, XEmacs will also search these
subdirectories in the `<root>/lib/xemacs-<VERSION>' subdirectory and
prefer directories found there.
By default, XEmacs does not have a pre-configured last package
hierarchy. Last hierarchies are primarily for using package hierarchies
of outdated versions of XEmacs as a fallback option. For example, it is
possible to run XEmacs 21.0 with the 20.4 package hierarchy as a last
hierarchy.
It is possible to specify at configure-time the location of the
various package hierarchies with the `--package-path' option to
configure. The early, late, and last components of the package path
are separated by double instead of single colons. If three components
are present, they are locate the early, late, and last package
hierarchies respectively. If two components are present, they locate
the early and late hierarchies. If only one component is present, it
locates the late hierarchy. At run time, the package path may also be
specified via the `PACKAGEPATH' environment variable.
An XEmacs package is laid out just like a normal installed XEmacs
lisp directory. It may have `lisp', `etc', `info', and `lib-src'
subdirectories. XEmacs adds these at appropriate places within the
various system-wide paths.
There may be any number of package hierarchy directories.
