Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Glyn Millington <glyn@millingtons.org>
Subject: Re: Installing Oort into /usr/local/stow
Date: Sun, 13 Apr 2003 06:28:40 +0100	[thread overview]
Message-ID: <87el47dkzb.fsf@millingtons.org> (raw)
In-Reply-To: <87k7dzb8o7.fsf@earthlink.net>

Rob French <fulcrum99lists@earthlink.net> writes:

> 1) Will ognus conflict with the gnus that ships w/ Emacs 21? I assume
>    there's a way to resolve that conflict.

In my .emacs (when I use Emacs21) I have 

;; for the latest greatest gnus.
(add-to-list 'load-path "~/elisp/gnus/lisp")
(add-to-list 'load-path "~/elisp/gnus/contrib")

Emacs then gets its gnus stuff from those directories rather - have not
experienced any problems.

Some other Oort-related things

;;; adds Oort info to tree!
(setq Info-directory-list (cons "~/elisp/gnus/texi/" Info-directory-list))
;;;they turned this on in Oort gnus
(setq gnus-agent nil)



>
> 2) So I've got oort from cvs in /usr/local/src/cvs/gnus. I do 
> "./configure --prefix=/usr/local", and then I do "make install
> prefix=/usr/local/stow/ognus". Finally, I do "stow ognus" from
> /usr/local/stow. That copies a bunch of files around, but is it
> sufficient?  

Try it and see - stow makes undoing the damage pretty straightforward
doesn't it? ;-)


hth





Glyn


       reply	other threads:[~2003-04-13  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87k7dzb8o7.fsf@earthlink.net>
2003-04-13  5:28 ` Glyn Millington [this message]
     [not found] ` <87fzomuuyw.fsf@gmx.net>
     [not found]   ` <87u1d1ub9c.fsf@earthlink.net>
2003-04-14  5:57     ` 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=87el47dkzb.fsf@millingtons.org \
    --to=glyn@millingtons.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).