It seems like Ruby's FileUtils.cp_r method especially was messing with some file
attributes, causing Emacs to print details about loading various elisp files on
startup. While when Emacs.app is copied into the output build directory using
"cp -a" instead of FileUtils.cp_r it does not exhibit this behavior.
It seems like Ruby's FileUtils.cp_r method especially was messing with some file attributes, causing Emacs to print details about loading various elisp files on startup. While when Emacs.app is copied into the output build directory using "cp -a" instead of FileUtils.cp_r it does not exhibit this behavior.