From 64a9de4f9f1b4db3115aa677ee7838fbe538070f Mon Sep 17 00:00:00 2001 From: Russell Martin Date: Wed, 24 Apr 2024 11:07:03 -0400 Subject: [PATCH] Update docs to reflect AppImages no longer depend on ``libcrypt.so.1`` --- changes/1383.feature.rst | 1 + docs/reference/platforms/linux/appimage.rst | 11 ----------- 2 files changed, 1 insertion(+), 11 deletions(-) create mode 100644 changes/1383.feature.rst diff --git a/changes/1383.feature.rst b/changes/1383.feature.rst new file mode 100644 index 000000000..2b8c10889 --- /dev/null +++ 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 index 0914b4612..fa94901eb 100644 --- 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 -`__. -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`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~