Re: problem startup xemacs 21.4 SuSE Linux 9.0

Mike FABIAN <[email protected]>
Newsgroups gmane.emacs.xemacs.general
Message-ID <[email protected]>
"Stephen J. Turnbull" <[email protected]> :

>>>>>> "philipp" == philipp sutter <[email protected]> writes:
>
>     philipp> I have the very same problem. and I posted this problem
>     philipp> allready. but no hint.
>
> You probably have two copies of the APEL package installed on your
> load-path.  This is called "shadowing."
>
> Use M-x list-load-path-shadows to find shadows.
>
> Typically this occurs in Linux distros which attempt to support
> distro-specific external packages by manipulating the load-path
> directly.  You may need to ask SuSE how to avoid picking up an APEL
> package that was installed to support GNU Emacs.

It is not for GNU Emacs actually, it is for XEmacs. It is a newer apel
required by the mail user agent "Wanderlust".

Alexander apparently has this apel-xemacs.rpm package installed, which
is intended to make recent versions of "Wanderlust" (package
wl-xemacs.rpm on SuSE Linux 9.0) work correctly.

apel-xemacs.rpm lives in /usr/share/xemacs/site-packages/ and
therefore shadows the apel in /usr/share/xemacs/xemacs-packages/ which
comes from the Sumos (xemacs-packages.rpm on SuSE Linux 9.0).

As soon as the apel in the Sumos is updated to a sufficiently recent
version, we could drop the additional apel-xemacs package again. 

But there was some discussion on the xemacs-beta mailing list
about updating apel in the Sumos, and as far as I understood
it, there were some difficulties.

The other solution would be to remove apel completely from
the Sumos, than one could always have the latest apel as an
external package.

If you don't use "Wanderlust" just don't install apel-xemacs and
wl-xemacs.  The warning is harmless though, you can also ignore it if
you want.

-- 
Mike FABIAN   <[email protected]>   http://www.suse.de/~mfabian
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.