Sorry for the continued cross-post. I'm not sure to which list this 
thread should migrate...

On Thursday, May 9, 2002, at 04:02 PM, David R. Morrison wrote:
> It has come up recently on this list and on fink-users that the 
> emacsen-common
> package is creating directories in /usr/local/share.  Christian 
> explained
> that these are where users are free to manually add elisp files, and 
> that
> he was avoiding having users place files under /sw without dpkg knowing
> about it.
>
> I would like to point out that /sw/etc is designed to contain files 
> which
> are not under dpkg's control.  (I'm sure that this is explained in the 
> docs
> somewhere, or at least that it used to be, but I can't locate it right 
> now.)
> Perhaps /sw/etc/emacs would be a more suitable location for these files?
The problem with this is (following debian's example) that /sw/etc/emacs 
is where emacsen-common-compliant packages install their startup 
scripts, which are included by emacs at launch-time. Additionally, each 
emacs program has its own directory (for version-specific startup stuff)

/sw/etc/emacs/site-start.d/...
/sw/etc/emacs21/site-start.d/...
/sw/etc/emacs20/site-start.d/...

I can see two possible ways to fix this (and am open to suggestions for 
better schemes):
1) Add a user-controlled site-lisp directory to each of the emacs 
directories. So the tree would now look like:
   /sw/etc/emacs/site-start.d/
                 /site-lisp
   /sw/etc/emacs21/site-start.d/
                   /site-lisp

2) Make /sw/etc/emacsen-common the startup-script directory, leaving 
/sw/etc/emacs for user-added files.


Problems with #1: having a directory with two similarly named 
subdirectories, one of which shouldn't be touched unless the user really 
knows what she is doing is kind of confusing.

Problems with #2: it's probably not an obvious place for people to look 
when they're trying to customize their startups. Plus the hierarchies 
get pretty long (e.g., /sw/etc/emacsen-common/emacs/site-
start.d/00fink-vars.el)...


I think my vote is with #1. But if there's a #3 that solves this in a 
semi-magical fashion I'd love to hear it...

-christian


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to