all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: mixed orgmode installation
Date: Sun, 08 Sep 2013 18:41:59 +0200	[thread overview]
Message-ID: <87d2ojs1t4.fsf@Rainer.invalid> (raw)
In-Reply-To: CA+M2ft9h3Bhd7offb8LbztGeht4b3Lv=bR9Rhw_Mbx_XWUBixQ@mail.gmail.com

John Hendy writes:
> Could you elaborate on this? I'd always thought the exact opposite due
> to being burned in the past by stale junk littered around /usr/lib,
> /usr/bin, /usr/local/[bin/sbin]. Thus, for some things, I prefer to
> run them from the git repository since I know where they'll be vs.
> where `make install` might desire to put them.

Git provides and manages the source tree and nothing else.  To get a
reliable Org you need a self-consistent and complete installation — that
is usually provided by the build system.

http://orgmode.org/worg/dev/org-build-system.html

The most logical place for that Org installation is site-lisp (since
then load-path is already set up correctly), but you can install almost
anywhere as long as you know where load-path is pointing to at all
times.  You could then have multiple versions of Org installed and use
them for different instances or versiosn of Emacs (one at a time,
obviously).

> What happens, for example, in this situation:
> - git clone
> - make && make install

You just need to "make install" and it's been that way for over two
years now…

> - some file.el gets moved from org.git/contrib/lisp to org.git/lisp in master
> - git pull
> - make && make install

And this is what "make up2" is doing, plus testing so the install won't
be attempted if the tests don't pass.

> Are there now two copies of file.el somewhere in the system?

No, unless you've changed the install location inbetween.  If a file
would be removed (or renamed), then you'd need to first issue a "make
clean-install" to make sure it is really gone from your installation.

> Anyway, if there's more to read on some of your situations, I'd love
> to know as I've been doing exactly that and want to stop if it's
> recommended against! Thanks for mentioning the potential risk, as I
> had no idea!

I'm not exactly sure what problem you are talking about, maybe you could
clarify.  In any case it seems there's been a mixup of different problems
in this thread.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2013-09-08 16:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 13:52 mixed orgmode installation Johannes Rainer
2013-09-04 14:19 ` Thorsten Jolitz
2013-09-04 14:52   ` Johannes Rainer
2013-09-04 15:07     ` Suvayu Ali
2013-09-08  5:40       ` adam
2013-09-08 14:37         ` John Hendy
2013-09-08 15:10           ` Suvayu Ali
2013-09-08 15:26             ` John Hendy
2013-09-08 16:52               ` Achim Gratz
2014-01-02  8:06                 ` Justin Gordon
2014-01-03  8:43                   ` Sharon Kimble
2014-01-03 18:08                     ` Justin Gordon
2014-01-03 18:49                   ` John Hendy
2013-09-04 19:20 ` Achim Gratz
2013-09-08 14:31   ` John Hendy
2013-09-08 16:41     ` Achim Gratz [this message]
2013-09-08 17:52       ` John Hendy
2013-09-08 18:39         ` 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

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

  git send-email \
    --in-reply-to=87d2ojs1t4.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.