Naming for appimage-extracted binary package for espanso-x11
The package espanso-x11-bin[1] exists, dropping an appimage without extracting it. Due to issues with the espanso code, FUSE can crash without cleaning up mount points, creating issues such as: cannot access '/tmp/.mount_espanshNkoOy': Transport endpoint is not connected This often hampers apps "save as" dialog boxes in /tmp -- GUI popups appear. So, I want to package a version of this that extracts the appimage, to avoid the FUSE issue. What should I call this? espanso-x11-appimage-extract-bin? # Ugly. Would the original be better named espanso-x11-appimage? [1] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=espanso-x11-bin -- Tom Hale
Hi Tom,
Due to issues with the espanso code, FUSE can crash without cleaning up mount points
Then the correct course of action is to file a bug against the upstream project. That way, everyone would benefit from the fix (as opposed to just the AUR users.)
So, I want to package a version of this that extracts the appimage, to avoid the FUSE issue. Here’s what the AUR submission guidelines [1] say:
Do not create duplicate packages.
It’s been consensus that creating a duplicate package just to fix one single bug is not acceptable. If you maintain an existing PKGBUILD, *temporarily* adding a patch to work around a bug can be fine. Duplicating the package is not. Regards Claudia [1]: https://wiki.archlinux.org/title/AUR_submission_guidelines
participants (2)
-
Claudia Pellegrino
-
Tom Hale