Achim Gratz <strom...@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.
