Packaging Org: how to put the newer version in load-path?

Packaging Org: how to put the newer version in load-path?

[Sean Whitton]

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Dear all,

I am presently packaging up Org from git for a new (to me) GNU/Linux
distribution I am switching to, CRUX [1], and I can’t figure out the
clean way to get the new version of Org in /usr/share/emacs/site-lisp to
override that in /usr/share/emacs/23.3.  I mean I could easily add it to
the front of my load-path in my own init file, but I don’t have to do
that on Arch Linux, which I am switching away from, because something
somewhere is adding it to the front of load-path for me.  What might
this be, so that I might duplicate this?  Is there a system-wide file
full of load paths for Emacs that I am missing?

Thanks.

S

[1] http://crux.nu/

-- 
Sean Whitton / <sean@silentflame.com>
OpenPGP KeyID: 0x3B6D411B
http://sean.whitton.me/


[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

Re: Packaging Org: how to put the newer version in load-path?

[Achim Gratz]

Sean Whitton <sean@silentflame.com> writes:
> I am presently packaging up Org from git for a new (to me) GNU/Linux
> distribution I am switching to, CRUX [1], and I can’t figure out the
> clean way to get the new version of Org in /usr/share/emacs/site-lisp to
> override that in /usr/share/emacs/23.3.  I mean I could easily add it to
> the front of my load-path in my own init file, but I don’t have to do
> that on Arch Linux, which I am switching away from, because something
> somewhere is adding it to the front of load-path for me.  What might
> this be, so that I might duplicate this?  Is there a system-wide file
> full of load paths for Emacs that I am missing?

This depends on how Emacs was configured.  The initial load-path is
defined in epath.h or can be overridden by an environment variable
EMACSLOADPATH. The invocation

emacs -Q -nw --batch --eval '(message "%s" load-path)'

tells you what the load-path is before running any startup scripts (if
subdirs.el is existing in any of the initial load-path directories, then
any subdirectories should have been expanded already).

The standard setup should be looking for

…/$VERSION/site-lisp
…/site-lisp
…/$VERSION/lisp
…/$VERSION/leim (maybe)

in that order (first version specific site-lisp, then site-lisp, then
the lisp that came with that installation of Emacs).  It could be
configured to use a different prefix for any site-lisp directories to
keep them separate from the installation.


HTH,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html