From: Gunnar Evermann <ge204@eng.cam.ac.uk>
Cc: ding@gnus.org
Subject: Re: Problem with the latest CVS build
Date: 06 Dec 1999 10:33:54 +0000 [thread overview]
Message-ID: <mqqvh6cjr3h.fsf@eng.cam.ac.uk> (raw)
In-Reply-To: Lloyd Zusman's message of "05 Dec 1999 18:24:07 -0500"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1615 bytes --]
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
next prev parent reply other threads:[~1999-12-06 10:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 8:12 Daniel Pittman
1999-12-04 8:31 ` Lars Magne Ingebrigtsen
1999-12-04 8:40 ` Daniel Pittman
1999-12-04 9:02 ` Shenghuo ZHU
1999-12-04 11:18 ` Mike Fabian
1999-12-04 13:27 ` William M. Perry
1999-12-05 0:21 ` Dave Love
1999-12-05 0:19 ` Dave Love
1999-12-05 1:45 ` Lloyd Zusman
1999-12-05 8:38 ` Hans de Graaff
1999-12-05 18:28 ` Lloyd Zusman
1999-12-05 18:41 ` Lloyd Zusman
1999-12-05 21:02 ` Hans de Graaff
1999-12-06 17:44 ` Hrvoje Niksic
1999-12-06 19:13 ` Jan Vroonhof
[not found] ` <ltr9h1s01u.fsf@ <byhfhvubli.fsf@urysohn.math.ethz.ch>
1999-12-07 8:20 ` Hrvoje Niksic
1999-12-07 12:27 ` Jan Vroonhof
1999-12-05 22:58 ` Kai Großjohann
1999-12-05 23:03 ` Lloyd Zusman
1999-12-05 23:24 ` Lloyd Zusman
1999-12-06 10:33 ` Gunnar Evermann [this message]
1999-12-06 15:48 ` Lloyd Zusman
1999-12-06 22:42 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mqqvh6cjr3h.fsf@eng.cam.ac.uk \
--to=ge204@eng.cam.ac.uk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).