Please dispose of merge request PRQ#45485. The maintainer of `beeper`, who is also comaintainer of `beeper-latest-bin`, and I coordinated to transition from `beeper` to `beeper-latest-bin`. The suffixes of the new package signify that this is an auto-updating package that installs the the most recent binaries (-latest-bin). While the -bin suffix may not be required for packages that do not have a source distribution, I know of no rule against using the -bin suffix for binary packages. Using these suffixes provides users with clarity about the nature of the package. The expectation for suffixless packages is that they are manually bumped, rather than auto updated. The original `beeper` package broke on a weekly basis because upstream uses a fixed download link with no alternative or redirect. The autoupdating package will not break as frequently, which is better for users. Merging `beeper-latest-bin` into `beeper` would also leave users without access to the underlying software because `beeper` is currently a metapackage that redirects users to `beeper-latest-bin`. Based on comment activity and out-of-date flags, many users have already successfully completed the migration. ----- yochananmarqos [1] filed a request to merge beeper-latest-bin [2] into

beeper [3]:

Upstream does not provide source code and the AppImage is the only source. No reason to use the '-bin' extension, let alone use 'latest' (as opposed to what?) in the name. A meta package is not necessary.

[1] https://aur.archlinux.org/account/yochananmarqos/ [2] https://aur.archlinux.org/pkgbase/beeper-latest-bin/ [3] https://aur.archlinux.org/pkgbase/beeper/