From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Yagnesh Raghava Yakkala <hi@yagnesh.org>,
Achim Gratz <Stromeko@nexgo.de>,
emacs-orgmode@gnu.org
Subject: Re: Meaning of install
Date: Tue, 12 Mar 2013 16:46:51 -0400 [thread overview]
Message-ID: <5650.1363121211@alphaville> (raw)
In-Reply-To: Message from tsd@tsdye.com (Thomas S. Dye) of "Tue, 12 Mar 2013 10:14:31 -1000." <m138w0pe8o.fsf@tsdye.com>
Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha Achim and Yagnesh Raghava Yakkala,
>
> Achim Gratz <Stromeko@nexgo.de> writes:
>
> >> 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.
>
> Yes, I think this structure needs to be reflected more clearly in the
> manual. I'll propose some new language when I get back to this.
>
Now that it's available, the "make install" method should probably be
described first in the documentation as the preferred method: it is
appropriate for the great majority of cases (Achim would probably say
"all cases").
Using the worktree is for diehard tinkerers, or old farts like me who
did it this way long before there was a build system and now don't want
to change our ossified ways.
> In the meantime, one more question. What are the considerations for the
> location of the worktree? If possible, I think it would be a good idea
> for the manual to make a recommendation for the worktree location and
> also provide a suitable warning about where *not* to put the worktree,
> if needed.
>
Like *any* worktree, It should be under one's home directory.
Nick
next prev parent reply other threads:[~2013-03-12 21:46 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 [this message]
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=5650.1363121211@alphaville \
--to=nicholas.dokos@hp.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=hi@yagnesh.org \
--cc=tsd@tsdye.com \
/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).