emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: local.mk and SUDO
Date: Sun, 29 Apr 2012 23:57:04 +0200	[thread overview]
Message-ID: <87zk9ukxqn.fsf@Rainer.invalid> (raw)
In-Reply-To: m2haw2iti4.fsf@btinternet.com

Martyn Jago writes:
> So the obvious answer is to not to use make install (as per the
> documentation). This is a heads-up to me since I believed install did
> more than simply moving .el and .elc files from A to B.

You can use "make install", but you must never install into the source
directory.  I'll check if changing the install mode to 644 is OK.

> However this is new behavior and worth mentioning. 'make install' (no
> sudo) used to silently `install' (or not as the case may be) and not
> change modes as above. Personally I wouldn't call it a regression though
> since make install is pointless IIUC in this situation.

If install were to use "cp", then you might even lose data when you try
to install into the same directory.  Don't do this, prefix must not
point to the git directory!

> Since I can no longer use `make up2' it seems that `make up1' is the
> correct command for my situation. This works fine except that
> org-version points to the wrong org-install:
>  Org-mode version 7.8.09
> (release_7.8.09-441-g6732d6.dirty @
> /Applications/Emacs.app/Contents/Resources/lisp/org/org-install.el.gz) 
> So for my case I've added the target upgrade to local.mk:
> upgrade: up1 autoloads


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

Samples for the Waldorf Blofeld:

      reply	other threads:[~2012-04-29 21:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 12:35 local.mk and SUDO Martyn Jago
2012-04-27 18:11 ` Achim Gratz
2012-04-27 20:02   ` Martyn Jago
2012-04-27 22:57     ` Achim Gratz
2012-04-29 12:59       ` Martyn Jago
2012-04-29 21:57         ` 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:

  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=87zk9ukxqn.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).