From: "Steven E. Harris" <seh@panix.com>
Subject: Re: The etc directory
Date: Thu, 07 Sep 2006 08:30:11 -0700 [thread overview]
Message-ID: <q94lkovd78s.fsf@chlorine.gnostech.com> (raw)
In-Reply-To: <microsoft-free.874pvkgr6i.fsf@youngs.au.com> (Steve Youngs's message of "Thu, 07 Sep 2006 15:51:33 +1000")
Steve Youngs <steve@sxemacs.org> writes:
> they'd rather put the files in the correct locations (as per XEmacs
> package hierarchy).
Which is where?
I've run into the same problem with trying to place the etc directory
on a fresh installation, using --prefix to put the CVS-pulled build
into ~/usr/local.
If I remember correctly, Gnus scans for its images by taking every
entry on the load path, popping up a directory (out of, say,
"site-packages/lisp/gnus" to "site-packages/lisp"), then looking for
"etc/gnus" below. For instance, gnus-xmas-glyph-directory is
initialized as follows:
(message-xmas-find-glyph-directory "gnus") ->
(nnheader-find-etc-directory "gnus")
-> "$PREFIX/lib/xemacs/site-packages/lisp/etc/gnus/"
In my current installation, I had to manually link
$PREFIX/lib/xemacs/site-packages/lisp/etc/ ->
$PREFIX/lib/xemacs/site-packages/etc/
for nnheader-find-etc-directory to work. Elsewhere, though,
gnus-group-startup-message calls (nnheader-find-etc-directory
"images/gnus"), which required me to create this link
$PREFIX/lib/xemacs/site-packages/etc/gnus ->
$PREFIX/lib/xemacs/site-packages/etc/images/gnus
to get things to work. Or maybe that last one wasn't necessary.
The function gmm-image-load-path-for-library also contains some
sniffing around under the etc directory.
I'm always reluctant to start from scratch for fear of having to
reestablish these links. What am I doing wrong?
--
Steven E. Harris
next prev parent reply other threads:[~2006-09-07 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 8:17 Didier Verna
2006-09-06 15:23 ` Miles Bader
2006-09-06 19:47 ` Didier Verna
2006-09-06 20:42 ` Reiner Steib
2006-09-07 5:51 ` Steve Youngs
2006-09-07 15:30 ` Steven E. Harris [this message]
2006-09-07 6:54 ` Didier Verna
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=q94lkovd78s.fsf@chlorine.gnostech.com \
--to=seh@panix.com \
/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).