emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Martyn Jago <martyn.jago@btinternet.com>
To: emacs-orgmode@gnu.org
Subject: Re: local.mk and SUDO
Date: Sun, 29 Apr 2012 13:59:15 +0100	[thread overview]
Message-ID: <m2haw2iti4.fsf@btinternet.com> (raw)
In-Reply-To: 87ipgkwzof.fsf@Rainer.invalid

Achim Gratz <Stromeko@nexgo.de> writes:

> Martyn Jago writes:
>>>> diff --git a/lisp/org-mobile.el b/lisp/org-mobile.el
>>>> old mode 100644
>>>> new mode 100755

[...]

> Then you yourself must most likely have changed the mode of those files
> to "executable".  There is nothing in the build system that even
> attempts to change modes.

Hi Achim

Since the new makefile uses the `install' command as opposed to `cp' to
install files, the following is noted in man install:

,----[*Man install*]
| -m      Specify an alternate mode.  The default mode is set to rwxr-xr-x
|         (0755).  The specified mode may be either an octal or symbolic value;
|         see chmod(1) for a description of possible mode values.
`----

Since the mode of .el files on git is 0644, this causes git to flag the
files as modified (since I am running Org from the distribution
directory).

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.

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.

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:

--8<---------------cut here---------------start------------->8---
 Org-mode version 7.8.09
(release_7.8.09-441-g6732d6.dirty @
/Applications/Emacs.app/Contents/Resources/lisp/org/org-install.el.gz) 
--8<---------------cut here---------------end--------------->8---

So for my case I've added the target upgrade to local.mk:

--8<---------------cut here---------------start------------->8---
upgrade: up1 autoloads
--8<---------------cut here---------------end--------------->8---

HTH

Best, Martyn


> Regards,
> Achim.

next prev parent reply	other threads:[~2012-04-29 12:59 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 [this message]
2012-04-29 21:57         ` 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

  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=m2haw2iti4.fsf@btinternet.com \
    --to=martyn.jago@btinternet.com \
    --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

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