From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: How do I create an XEmacs package from CVS Gnus?
Date: Sat, 18 Aug 2001 23:03:08 -0500 [thread overview]
Message-ID: <q6msneowvb7.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <8666bku52a.fsf@duchess.twilley.org> (Jack Twilley's message of "Sat, 18 Aug 2001 20:00:45 -0700")
>>>>> On Sat, 18 Aug 2001 20:00:45 -0700,
>>>>> Jack Twilley <jmt+usenet@twilley.org> (jack) writes:
jack> I'd love to install my CVS Gnus "properly".
jack> That means using the package install tools. Does anyone else do this?
jack> It would be cool for those of us who don't always have root where we
jack> read our email.
You can install it into ~/.xemacs/xemacs-packages/. I just
configure as follows:
./configure \
--infodir=$HOME/.xemacs/xemacs-packages/info \
--with-lispdir=$HOME/.xemacs/xemacs-packages/lisp/gnus \
--with-etcdir=$HOME/.xemacs/xemacs-packages/etc
Though, I usually just remove the info/dir that gets installed as
xemacs seems to be able to build an index on the fly okay.
--
Amos
prev parent reply other threads:[~2001-08-19 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 3:00 Jack Twilley
2001-08-19 4:03 ` Amos Gouaux [this message]
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=q6msneowvb7.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/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).