From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: M-x org-version RET now produces some sensible in all possible install/use-cases
Date: Fri, 18 May 2012 22:14:40 +0200 [thread overview]
Message-ID: <871umhcklr.fsf@Rainer.invalid> (raw)
In-Reply-To: 87k40axa0a.fsf@gnu.org
Bastien writes:
> Thanks to patient and hard work of Achim, M-x org-version RET
> should now return something sensible in each use-case.
There are basically two use-cases, not-installed and installed.
Not-installed comes in three flavors, although the first one has some
hard to avoid pitfalls and should be considered dangerous. If the
autoload files are not or not fully generated, then determining the
version is done at runtime like in former org versions and relies on the
existence of $(lispdir)/../UTILITIES/org-fixup.el — if that can't be
found either, a default "N/A" version string will be output (which
should only be possible if somehow the lisp directory from org has been
copied by hand someplace else).
1) Org uninstalled (and possibly uncompiled) from Git or tarball.
1a) No org-version.el or org-install.el exists in worktree. Partially
supported configuration, org version is determined from git if possible
via UTILITIES/org-fixup.el. However, Emacs versions delivered with
orgmode will provide autoloads that may or may not work with that
version of org (mixed installation). If such a situation is
encountered, warn the user. It can work if the autoloads from the
installation match the ones that would be generated for the worktree,
which generally is only the case if there is a relatively recent
installation in site-lisp.
1b) Autoload file org-install.el exists in worktree, but not
org-version.el. Fully supported configuration, org version is
determined from git if possible via UTILITIES/org-fixup.el.
1c) Both org-version.el or org-install.el exist in worktree.
Recommended configuration for 1), org version is taken from
org-version.el (git never gets invoked).
2) Org installed. Both org-version.el and org-install.el must exist
in install directory. Only supported configuration for 2), org
version is taken from org-version.el (git never gets invoked since
UTILITIES/org-fixup.el is not available).
Any unsupported configuration should still yield a version string, but
it will contain "N/A" to alert the user about a botched org
installation.
If "N/A" or a wrong version number is shown from 'M-x org-version' or the
path shown after the Git version is not what it should be or you see a
"mixed installation!" there, then please check with 'M-x locate-library'
where org, org-install and org-version are found (or that they are _not_
found at all, depending on which use case above you are targeting). If
they are found, they must all be found in the same directory.
If you have leftover files from an older installation, re-configure
load-path so that Emacs doesn't find them, remove them altogether if
they are expendable or do a 'make cleanall' if they are in the org
directory. From there, pick your use-case and try to stick to it (or at
least do another 'make cleanall' before you switch).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
prev parent reply other threads:[~2012-05-18 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 6:45 M-x org-version RET now produces some sensible in all possible install/use-cases Bastien
2012-05-18 19:25 ` Thomas S. Dye
2012-05-18 19:41 ` Achim Gratz
2012-05-18 23:41 ` Thomas S. Dye
2012-05-19 8:48 ` [PATCH] " Achim Gratz
2012-05-19 8:52 ` Bastien
2012-05-19 17:41 ` Thomas S. Dye
2012-05-19 18:02 ` Achim Gratz
2012-05-18 20:14 ` Achim Gratz [this message]
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=871umhcklr.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).