emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sean Whitton <sean@silentflame.com>
To: emacs-orgmode@gnu.org
Subject: Packaging Org: how to put the newer version in load-path?
Date: Thu, 07 Jul 2011 10:35:50 +0100	[thread overview]
Message-ID: <87pqlmh1qh.fsf@zephyr.silentflame.com> (raw)

[-- 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?



[1] http://crux.nu/

Sean Whitton / <sean@silentflame.com>
OpenPGP KeyID: 0x3B6D411B

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

             reply	other threads:[~2011-07-07  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07  9:35 Sean Whitton [this message]
2011-07-07 16:42 ` Packaging Org: how to put the newer version in load-path? Achim Gratz

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pqlmh1qh.fsf@zephyr.silentflame.com \
    --to=sean@silentflame.com \
    --cc=emacs-orgmode@gnu.org \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).