Stable urls for beeper - https://download.todesktop.com/2003241lzgn20jd/beeper-$VERSION.AppImage
https://github.com/NixOS/nixpkgs/pull/241992#issuecomment-1656884024
Search Criteria
Package Details: beeper-latest-bin 4.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/beeper-latest-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | beeper-latest-bin |
| Description: | metapackage - migrate to beeper-v4-bin |
| Upstream URL: | None |
| Submitter: | xiota |
| Maintainer: | xiota (sundbp) |
| Last Packager: | xiota |
| Votes: | 10 |
| Popularity: | 0.33 |
| First Submitted: | 2023-07-28 06:12 (UTC) |
| Last Updated: | 2025-05-16 23:07 (UTC) |
jshcmpbll commented on 2023-08-03 21:11 (UTC)
sundbp commented on 2023-07-31 07:54 (UTC)
@xiota: I have zero experience with auto-updating packages so very happy to be guided by your opinion regarding version bumps. It's actually not been too bad to update this package. I have it running most of the time while working so whenever I see a popup I updated the 2 values (version and sha256sum) and pushed. What was more annoying was when an update happened when I was travelling or something and it broke for others while I wasn't likely to be at a computer for a while. As that bit is now gone with an evergreen package the version bump itself seems fine to update more monthly/quarterly or even less often depending on how fast the upstream numbers change.
xiota commented on 2023-07-29 14:53 (UTC) (edited on 2023-07-29 15:01 (UTC) by xiota)
Re: the request to merge into beeper
The maintainer of beeper (also comaintainer of this package) and I have coordinated to transition from beeper to beeper-latest-bin. The suffixes signify that this is an auto-updating package (latest) that installs binaries (bin).
The expectation for a suffixless package is that the versions would be bumped manually, rather than auto updated. The package would also break each week because upstream uses download links that do not contain version numbers.
While the -bin suffix may not be required for packages that do not have a source distribution, there is no rule against using the suffix, and it does serve to notify users of the nature of the package. There are many existing packages using the -bin suffix in the absence of a source distribution. Using the suffix also prevents having to refactor packages should upstream decide to release the source.
xiota commented on 2023-07-28 15:36 (UTC)
@shalzz No problem. Feel free to comment if you have any other issues.
shalzz commented on 2023-07-28 15:16 (UTC)
Ah, makes sense. I wasn't aware of the desktop file persistent across upgrades via ~/.local/share/applications. Thanks!
xiota commented on 2023-07-28 15:13 (UTC)
I'm inclined to leave the .desktop file alone because users can already create customized copies in ~/.local/share/applications.
sundbp commented on 2023-07-28 14:23 (UTC)
@xiota: all is well now - with the change on the -latest-bin side and the epoch set it installs ok as beeper now so people upgrading will have a smooth ride. Thanks for the help on this!
sundbp commented on 2023-07-28 11:48 (UTC)
Btw, I had the same experience with the frame option. Forgot to reply to that message. Didn't seem a good default.
sundbp commented on 2023-07-28 11:46 (UTC)
@xiota: tried with yay after a similar thought with makepkg.ill add the epoch in a little bit.
Pinned Comments
xiota commented on 2025-05-02 20:35 (UTC)
This package will be retired in favor of
aur/beeper-v4-bin. It has been converted into a metapackage to assist users with migration before its eventual deletion.