Carbon.

[Didier Verna]

Aidan Kehoe <kehoea at parhasard.net> wrote:

> Well, in the Mac Carbon paradigm, which is the most sensible paradigm
> for desktop machines, the âœsite-specific❠idea is kind of
> irrelevant. So I donâ™t think there exists a particularly clean way
> to do this, and if weâ™re going to do ugly hacks, linking
> /usr/local/lib/xemacs/xemacs-packages to ~/.xemacs/xemacs-packages is
> probably the simplest and most effective approach.
>
> I suppose though it would make sense and be more userfriendly to look at the
> most commonly used prefixes to see if the corresponding directories exist;
> on my machine I have /usr/local (general GNU stuff built from source) and
> /opt/local (DarwinPorts); are there further conventions for these things on
> OS X?

  Hmm, I think we did not understand each other. What I meant was:

1/ if the carbon executable is to adhere to the Mac OS way (for as much
  as I can figure it out), it probably should try to find packages in
  $HOME/Library/Application Support/XEmacs, and then in
  /Library/Application Support/XEmacs/ (and I mean, it should probably
  find mule-packages xemacs-packages and site-packages subris in both
  these direcotries).

2/ I have an XDarwin XEmacs using the normal Unix scheme which is to
  look for packages in ~/.xemacs/ and in /usr/local/share/xemacs. What I
  meant was that it would be easy to make both XEmacsen coexists without
  replicating the packages structure, like this:

  ln -s /usr/local/share/xemacs /Library/Application Support/XEmacs
  ln -s $HOME/.xemacs $HOME/Library/Application Support/XEmacs

-- 
New @-quartet featured CD Review !!
http://www.indie-music.com/modules.php?name=News&file=article&sid=6457

Didier Verna, didier at lrde.epita.fr, http://www.lrde.epita.fr/~didier

EPITA / LRDE, 14-16 rue Voltaire   Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France   Fax.+33 (1) 53 14 59 22   didier at xemacs.org