emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vicente Vera <vicentemvp@gmail.com>
To: Stromeko@nexgo.de, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Installing from git
Date: Wed, 2 Jul 2014 22:52:32 -0400	[thread overview]
Message-ID: <CAMfbzvCqQ8n_VGjjy=xm3+yHjNZZDXy5QCzmf_cAv4sBKgk1Qw@mail.gmail.com> (raw)

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

Thank you for your replies, I think i'm beginning to understand the
process. These are the changes I made to local.mk:

prefix  = /usr/local/share
datadir = /usr/local/share/emacs/24.4.50/etc/org (actually, this directory
belongs to the built-in Org installation)

Then:
$ make
$ sudo make install

And it worked fine. The info manual is now updated, so is everything else.

So, overall, the purpose of running 'make install' (or 'make up2', to also
pull from the Git repository) is to avoid overriding the default Org
installation that comes with Emacs?

Going through the variables in local.mk it seems this is the idea, except
maybe for 'infodir' which in my case points to the place where Emacs threw
all its info files (including Org).

To sum up, the process made the following changes on my system:
- Org lisp files from Git now reside in /usr/local/share/emacs/site-lisp
(which is in load-path by default). The original built-in Org lisp files
are untouched.
- M-x org-version shows the correct updated version and location.
- M-x info shows the updated info manual which now resides in
/usr/local/share/info (I think it replaced the built-in manual?).
- Org data files now reside in /usr/local/share/emacs/24.4.50/etc/org
(replacing the built-in files?).

No extra elisp code was needed (adding the cloned repository to load-path,
etc.).

[-- Attachment #2: Type: text/html, Size: 1531 bytes --]

             reply	other threads:[~2014-07-03  2:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03  2:52 Vicente Vera [this message]
2014-07-03 16:46 ` Installing from git Achim Gratz
  -- strict thread matches above, loose matches on Subject: below --
2015-05-15  0:35 Installing from Git Vicente Vera
2015-05-14 13:04 Marcin Borkowski
2015-05-14 13:33 ` Marcin Borkowski
2015-05-14 13:43   ` Jorge A. Alfaro-Murillo
2014-06-30 22:44 Installing from git Vicente Vera
2014-06-30 22:51 ` John Hendy
2014-07-01 17:21   ` Achim Gratz
2014-07-01 21:32     ` John Hendy
2014-07-01 20:16   ` Vicente Vera
2014-07-02 17:17     ` Achim Gratz
2014-07-02 18:25 ` Miguel Ruiz
2014-07-02 20:31   ` Achim Gratz
2014-07-02 20:29 ` Jorge A. Alfaro-Murillo
2014-07-02 20:39   ` Achim Gratz
2014-07-02 21:17     ` Jorge A. Alfaro-Murillo
2014-07-03 16:40       ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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='CAMfbzvCqQ8n_VGjjy=xm3+yHjNZZDXy5QCzmf_cAv4sBKgk1Qw@mail.gmail.com' \
    --to=vicentemvp@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).