Merge pull request #1750 from rmartin16/libcrypt-docs

Update docs to reflect AppImages no longer depend on ``libcrypt.so.1``
beeware · Apr 25, 2024 · 178a1e6 · 178a1e6
2 parents 5a38a63 + 64a9de4
commit 178a1e6
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 11 deletions.
diff --git a/changes/1383.feature.rst b/changes/1383.feature.rst
@@ -0,0 +1 @@
+Apps packaged as AppImages are no longer dependent on ``libcrypt.so.1``.
diff --git a/docs/reference/platforms/linux/appimage.rst b/docs/reference/platforms/linux/appimage.rst
@@ -239,17 +239,6 @@ Packaging on Linux is a difficult problem - especially when it comes to binary
 libraries. The following are some common problems you may see, and ways that
 they can be mitigated.
 
-Missing ``libcrypt.so.1``
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The support package used by Briefcase has a `number of runtime requirements
-<https://gregoryszorc.com/docs/python-build-standalone/main/running.html#runtime-requirements>`__.
-One of those requirements is ``libcrypt.so.1``, which *should* be provided by
-most modern Linux distributions, as it is mandated as part of the Linux Standard
-Base Core Specification. However, some Red Hat maintained distributions don't
-include ``libcrypt.so.1`` as part of the base OS configuration. This can usually
-be fixed by installing the ``libxcrypt-compat`` package.
-
 Failure to load ``libpango-1.0-so.0``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~