From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Meaning of install
Date: Tue, 12 Mar 2013 20:02:24 +0100 [thread overview]
Message-ID: <87y5dso30f.fsf@Rainer.invalid> (raw)
In-Reply-To: m1ppz4pptx.fsf@tsdye.com
Thomas S. Dye writes:
> Section 1.2 of the Org manual in git is called `Installation', and it
> includes instructions on three ways `to install Org on top' of the Org
> that ships with Emacs.
>
> Near the bottom of that page, after giving instructions on how to
> install Org from the git repository, it says that "You can also ...
> install Org with `make install'."
>
> This is confusing to a User like me. After having been given
> instructions on how to install Org:
>
> $ cd ~/src/
> $ git clone git://orgmode.org/org-mode.git
> $ make autoloads
>
> I now find that I can also install with `make install.'
Make a suggestion. When the new build system went live I had adapted
the description with explicit instructions for each installation method,
which was later simplified (a touch too much for my tastes) by Bastien —
which is what you look at now. It actually doesn't even work as
documented, I see now.
> It seems clear to me that `install' is being used in two different senses
> here. I'd like to disambiguate--can someone suggest a concise way to do
> this?
Using Org from Git can be done in two fundamentally different ways:
a) using the worktree directly as your installation,
b) using it as the source for an installation in a different place.
Installation is used here in the sense that your Emacs runs the
"installed" code.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-03-12 19:12 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 [this message]
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
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=87y5dso30f.fsf@Rainer.invalid \
--to=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).