From: tsd@tsdye.com (Thomas S. Dye)
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Meaning of install
Date: Thu, 14 Mar 2013 07:04:18 -1000 [thread overview]
Message-ID: <m1sj3xkj59.fsf@tsdye.com> (raw)
In-Reply-To: <87d2v34vij.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 13 Mar 2013 08:19:16 +0100")
Aloha all,
Thanks for your help and patience as I try to find the simplest, most
widely applicable, path to a successful Org installation.
I've decided not to mention el-get in the manual. It looks like a great
power-user tool, but I don't think it fits here. Perhaps something on
Worg (if it's not already there)?
Here is the most recent version:
1.2.3 Use the Org git repository
--------------------------------
You can clone the development version of the Org git repository,
typically to a location under your home directory. The example in this
section assumes this location is `src/' in your home directory:
$ cd ~/src/
$ git clone git://orgmode.org/org-mode.git
$ cd org-mode
In most cases where you have permission to write to system locations,
you will probably want to install Org with the Emacs system files.
This is a system-specific operation that is guided by a file,
`local.mk', which you must ensure is configured properly. First,
generate a `local.mk' template with the command `make local.mk'. Edit
`local.mk' following the instructions in the file, and save it.(1)
Finally, run `make install' to build all of Org and install it. The
command `make help' provides a full list of options for the build
system.
If you would like to run Org from the clone location, instead of
installing it with the Emacs system files, you can simply run `make
autoloads' and set the load-path in your `.emacs'. Using the example
location, add this to `.emacs':
(add-to-list 'load-path "~/src/org-mode/lisp")
If your installation has special requirements, please refer to the
detailed description of the capable build system at the Org Build
System page (http://orgmode.org/worg/dev/org-build-system.html).
---------- Footnotes ----------
(1) The `local.mk' template is designed to work out of the box with
GNU systems.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-03-14 17:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:04 Meaning of install Thomas S. Dye
2013-03-12 18:27 ` Yagnesh Raghava Yakkala
2013-03-12 19:02 ` Achim Gratz
2013-03-12 20:14 ` Thomas S. Dye
2013-03-12 20:29 ` Achim Gratz
2013-03-12 20:46 ` Nick Dokos
2013-03-13 4:05 ` Thomas S. Dye
2013-03-13 7:19 ` Achim Gratz
2013-03-13 8:00 ` Andreas Röhler
2013-03-13 8:43 ` Bastien
2013-03-13 9:11 ` Andreas Röhler
2013-03-13 11:56 ` Bastien
2013-03-14 20:29 ` Andreas Röhler
2013-03-13 8:00 ` Yagnesh Raghava Yakkala
2013-03-14 17:04 ` Thomas S. Dye [this message]
2013-03-14 17:24 ` Bastien
2013-03-14 19:03 ` Achim Gratz
2013-03-14 20:15 ` Thomas S. Dye
2013-03-15 21:25 ` Bastien
2013-03-15 23:06 ` Thomas S. Dye
2013-03-13 8:56 ` Bastien
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=m1sj3xkj59.fsf@tsdye.com \
--to=tsd@tsdye.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).