stop existing, possibly in favor of briefcase

[glyph]

briefcase issues that would need to be resolved to kill Encrust completely:

• overly aggressive restriction on bundle identifiers restricts my idiom beeware/briefcase#1212
• macOS apps aren't portable across x86_64/M1 unless all binary wheels are universal2 beeware/briefcase#1217
• maybe briefcase might hypothetically generate an archive invalid for notarization sometimes when using a zip archive for mac app distribution, and should probably use the recommended command to generate them beeware/briefcase#1218
• Parallelise calls to app signing beeware/briefcase#1201
• codesign --deep is deprecated and should be removed beeware/briefcase#1221
• allow for bundling 3rd-party platform-specific frameworks (on macOS) beeware/briefcase#2180
• sign with Sparkle and generate appcasts
• investigate briefcase bundle size to see if it's a problem #10
• Improve customizability of Apple code signing process beeware/briefcase#1291 — specifically the bit about custom Info.plist keys; right now both of my apps need at least LSUIElement, but likely will need more

[glyph]

maybe also need codesigning-without-building-using-briefcase documentation, but I gather this is already at least possible and maybe the docs even exist, need to read up on that before filing anything there

[freakboy3742]

FYI: beeware/briefcase#2110 (currently in review) resolves the last of your blockers. If there's anything else standing in the way of Briefcase adoption, let us know.

[glyph]

At this point I think this is going to start coming down to the features of py2app, rather than encrust itself. Is there a tutorial for anywhere to use briefcase just for codesigning and archiving, on an existing app bundle? It would be easier to adopt it a bit at a time.

[glyph]

Oh wait I guess I can't quite just use it for codesigning, because I would need some way to invoke the code in beeware/briefcase#1217 too, hmm.

[freakboy3742]

Yeah - you could probably trick Briefcase into thinking it had created the app, and so it could then sign it - but I wouldn't give any guarantees that any trick would be reliable in the long term - what you're describing definitely isn't an officially supported use case.

[glyph]

@freakboy3742 Trying to describe the major things that I think I'm still getting out of py2app.