Update py2app discussion in README

Sun, 05 Dec 2021 15:25:51 +0200

author
Tuomo Valkonen <tuomov@iki.fi>
date
Sun, 05 Dec 2021 15:25:51 +0200
changeset 140
a70ba964f455
parent 139
84b041f6f7f3
child 141
a1c97bc1789e

Update py2app discussion in README

README.md file | annotate | diff | comparison | revisions
--- a/README.md	Sun Dec 05 15:08:50 2021 +0200
+++ b/README.md	Sun Dec 05 15:25:51 2021 +0200
@@ -74,19 +74,18 @@
 To permanently authenticate Borgend to use the keychain, and therefore not
 have to enter the keychain password every time Borgend is launched, it is
 useful to encapculate it into a macOS app. This can be done with
-
- - [py2app](https://py2app.readthedocs.io/en/latest/install.html).
+[py2app](https://py2app.readthedocs.io/en/latest/install.html).
+To create a standalone app that you can launch at startup and give permanent
+permissions to the keychain, use
 
-To create an app that you can launch at startup and give permanent permissions
-to the keychain, use
-
-    python3 setup.py py2app -A
+    python3 setup.py py2app
 
 The app hould be placed under `dist/`. Copy it to your `Applications`
 directory, and set it up to launch on login.
 
-If you are keen on wasting your life, you can try to run py2app without the
-`-A` option to create a standalone app that you can copy to computers without
-Python installed. This will, however, most likely not work because py2app
-is shit. Currently (2018-09-18) it is not working with the keyring package.
+Py2app is _flaky_ to say the least. If the positions of sunspots so dictate,
+the above command may not create a working standalone application. If this is
+the case, you may attempt to add the `-A` option to the command. It will
+then create a non-standalone application. While not easily transferrable
+between different machines, it will still help with keychain permissions.
 

mercurial