From 4b9190fc29aec0f005f08c0269bb9ff081f19fe3 Mon Sep 17 00:00:00 2001 From: Christian Lohmaier Date: Mon, 18 Jan 2021 11:01:48 +0100 Subject: mac: don't put script files into Contents/MacOS or framework-bin directory MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signing them as executable code would require external attributes, and those in turn break packaging into hfs+ dmg when building on apfs with Big Sur. It is not a new thing - the old Code Signing in Depth technote https://developer.apple.com/library/archive/technotes/tn2206/_index.html already reads: "Store Python, Perl, shell, and other script files and other non-Mach-O executables in your app's Contents/Resources directory. While it's possible to sign such executables and store them in Contents/MacOS, this is not recommended. […] Put another way, a properly-signed app that has all of its files in the correct places will not contain any signatures stored as extended attributes." The patch does exactly that for LO and the shipped python framework and adds symlinks for the moved files. Same applies for the Language pack applescript and the tarball - those are also moved into Contents/Resources Change-Id: Iab21e77b73f941248ca89c6e80703fdf67a1057c Reviewed-on: https://gerrit.libreoffice.org/c/core/+/109537 Tested-by: Jenkins Reviewed-by: Christian Lohmaier --- setup_native/scripts/mac_install.script | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'setup_native') diff --git a/setup_native/scripts/mac_install.script b/setup_native/scripts/mac_install.script index 57609636e2c0..eb92d70ba982 100644 --- a/setup_native/scripts/mac_install.script +++ b/setup_native/scripts/mac_install.script @@ -24,4 +24,4 @@ MY_DIR=$(dirname "$0") -osascript "$MY_DIR/osx_install.applescript" +osascript "$MY_DIR/Resources/osx_install.applescript" -- cgit v1.2.3