From: Eli Zaretskii <eliz@gnu.org>
To: Jim Myhrberg <contact@jimeh.me>
Cc: alan@idiocy.org, contact@jimeh.me, 49271@debbugs.gnu.org
Subject: bug#49271: 28.0.50: native-comp: Signing macOS self-contained .app bundle fails due to new *.eln location
Date: Wed, 30 Jun 2021 15:20:41 +0300 [thread overview]
Message-ID: <83zgv7mtly.fsf@gnu.org> (raw)
In-Reply-To: <CAGaZ61uipOOVTo1-6wGsUn3+Apsqe+eXKyYQ8VKaL27ZCoXXKw@mail.gmail.com> (message from Jim Myhrberg on Wed, 30 Jun 2021 11:04:43 +0100)
> From: Jim Myhrberg <contact@jimeh.me>
> Date: Wed, 30 Jun 2021 11:04:43 +0100
>
> I've just tried "Contents/lib", and it allowed me to sign and notarize
> the .app bundle. And combined with your patch from bug#49270, all
> bundled *.eln files are also correctly located and loaded :)
>
> I did a bit of searching myself for alternatives and found
> "Contents/PlugIns" as a potentially suitable place, but a quick test
> revealed codesign fails the same way with it as it does with
> Contents/MacOS.
>
> Personally I think Contents/lib is probably fine, as both codesign and
> Apple's notarization process are happy with it. And the notarization
> process seems very picky. For example, when *.eln files were in
> Resources/native-lisp, my initial notarization attempts failed because
> it considered the *.eln files to be binaries, and they had not been
> signed by codesign despite the --deep flag being used. Hence I'm
> individually signing all the *.eln files before signing the app bundle
> itself to get the app through notarization.
The *.eln files are shared libraries. What is the canonical place to
install shared libraries specific to an application?
next prev parent reply other threads:[~2021-06-30 12:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 11:58 bug#49271: 28.0.50: native-comp: Signing macOS self-contained .app bundle fails due to new *.eln location Jim Myhrberg
2021-06-29 19:18 ` Alan Third
2021-06-30 10:04 ` Jim Myhrberg
2021-06-30 12:20 ` Eli Zaretskii [this message]
2021-06-30 12:39 ` Jim Myhrberg
2021-06-30 12:52 ` Alan Third
2021-06-30 13:10 ` Jim Myhrberg
2021-06-30 19:05 ` Alan Third
2021-07-01 7:13 ` Eli Zaretskii
2021-07-01 18:45 ` Alan Third
2021-07-01 19:03 ` Eli Zaretskii
2021-07-01 19:56 ` Alan Third
2021-07-01 14:53 ` Jim Myhrberg
2021-07-01 20:13 ` Alan Third
2021-07-01 20:43 ` Jim Myhrberg
2021-07-01 21:16 ` Alan Third
2021-06-30 12:42 ` Alan Third
2021-06-30 12:51 ` Jim Myhrberg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zgv7mtly.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49271@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=contact@jimeh.me \
/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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.