From: Pieter Wenk <pwenk@urbanet.ch>
Subject: Re: Updating to gnus 5.8.2
Date: Wed, 29 Dec 1999 20:00:38 +0100 [thread overview]
Message-ID: <19991229200038.A3308@sre-4-139.urbanet.ch> (raw)
In-Reply-To: <9t9puvxwy5u.fsf@mraz.iskon.hr>
On jeu, 23 déc 1999, Hrvoje Niksic wrote:
Hello Hrvoje,
You may laugh, but I have not as yet suceeded in
getting on work the 5.8.2 gnus version.
Let me explain what is done:
The first installation went for xy reasons wrong.
Consequently I fired a script Robin was so kind
letting me have:
#!/bin/sh
# NQA suicidal Gnus script - use at your own risk!
## Definition des Quell- und der Zielverzeichnisse
BACKUPDIR=/usr/tmp/gnus.BACKUP
SOURECEDIR=/usr/tmp/gnus-5.8.2/ # IST ES DA???
TARGET_TOP=/usr/local/lib/xemacs/xemacs-packages/
TARGET_ELISP=$TARGET_TOP/lisp/
TARGET_ETC=$TARGET_TOP/etc/
TARGET_INFO=$TARGET_TOP/info/
## Gnus bauen
cd $SOURECEDIR && ./configure && make EMACS=xemacs
echo "Gnus built"
## Backup machen
mkdir $BACKUPDIR/info/
mv $TARGET_ELISP/gnus $BACKUPDIR
mv $TARGET_ETC/gnus $BACKUPDIR
mv $TARGET_INFO/gnus* $BACKUPDIR/info/
echo "Backup done"
## Symlinks legen
cd $TARGET_ELISP && ln -s $SOURECEDIR/ gnus
cd $TARGET_ETC && ln -s $SOURCEDIR/etc/gnus/ gnus
cd $TARGET_INFO && ln -s $SOURCEDIR/texi/gnus* .
echo "symlinks made"
## EOF ==================================================
OK, this worked perfectly, now I have:
In:
/usr/tmp/gnus-5.8.2 what has been absolutly
correctly compiled and:
in:
/usr/local/lib/xemacs/xemacs-packages/lisp/gnus/gnus-5.8.2/lisp/
other files, which seems to be indentical with the above.
Now I want to link all this with ln -s:
I guess
ln -s usr/tmp/gnus-5.8.2/lisp/ ls -s /usr/local/lib/xemacs/xemacs-packages/lisp/gnus/gnus-5.8.2/lisp/
should be the link.
Is this correct ???
Secondly:
Do I have to enter the following path in ~/.emacs
setq load-path (cons (expand-file-name
"/usr/local/lib/xemacs/xemacs-packages/lisp/gnus/gnus-5.8.2/lisp")
load-path))
BTW I have meanwhile also upgraded my xemacs version to Bryce Canyon
which works fine....
I would be pleased using now this new version. Unfortunately
all this is not quite transparent...
Many thanks for your help
Regards
--
/ / (_)____ __ ____ __
Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland
/____/_/_//_/\_,_/ /_/\_\
next prev parent reply other threads:[~1999-12-29 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 13:56 Pieter Wenk
1999-12-09 14:05 ` Hrvoje Niksic
1999-12-09 14:40 ` Jørgen Wahlberg
1999-12-10 13:55 ` Pieter Wenk
1999-12-23 12:21 ` Pieter Wenk
1999-12-23 12:58 ` Laura Conrad
1999-12-23 14:05 ` Hrvoje Niksic
1999-12-29 19:00 ` Pieter Wenk [this message]
1999-12-29 20:34 ` Kai Großjohann
1999-12-23 13:57 ` Kai Großjohann
1999-12-23 14:01 ` Hrvoje Niksic
1999-12-23 22:57 ` Pieter Wenk
1999-12-23 23:45 ` 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=19991229200038.A3308@sre-4-139.urbanet.ch \
--to=pwenk@urbanet.ch \
/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).