Lloyd Zusman <ljz@asfast.com> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
> > Lloyd Zusman <ljz@asfast.com> writes:
> > 
> > > Well, I'm using XEmacs, which means that `mailheader' is part of its
> > > `gnus' package.  But I'm not using the XEmacs distribution of gnus,
> > > but rather, the CVS version.  Therefore, I don't have access to
> > > `mailheader'.
> > 
> > Why don't you install the normal Gnus package and then add the CVS
> > Gnus?  Just put the CVS Gnus directory first in load-path, and Bob
> > will be your uncle.
> 
> I have done exactly that, but the standard building procedure that
> gets downloaded with CVS doesn't know about my normal load path, and
> it can't find mailheader in the load path that *it* tries to use.


strange, can you post the output of something like:
  xemacs -batch -q -no-site-file -eval '(print load-path)' | tr ' ' '\n' | grep gnus


I get:
"/home/tigger3/ge204/.xemacs/xemacs-packages/lisp/pgnus-cvs/"
"/tools/emacs/lib/xemacs/xemacs-packages/lisp/gnus/"


where the first is a link to the CVS version's gnus/lisp directory and
the second is the normal XEmacs Gnus package (currently using Gnus
5.6.44 or somesuch). Thus the normal users get the old XEmacs package
and I get the bleeding edge CVS snapshots.

This setup is certainly not perfect (e.g. I guess the auto-autoload.el
should be rebuilt by Gnus' Makefile) but it Works For Me(tm).

BTW, we are still looking for a volunteer to package Gnus5.8.x for
XEmacs :-)

 Gunnar

-- 
       Gunnar Evermann
Speech, Vision & Robotics Group
Cambridge University Engineering Department