Arch Linux User Repository

Switching back to the system electron because of reported issues with the packaged electron. Also, fixed pkgver issue.

Build options by setting environment variables (or editing pkgbuild):

• _system_electron=false – Use the packaged electron
• _electron_version=29 – Use a specific system electron version (when default version has problems)
  • Or edit /usr/bin/beeper after install.
• _install_path=usr/lib – Use a different install path. Default is opt. (Do not include leading / and trailing /beeper.)

This is a self-updating package. It always downloads the latest available AppImage and applies the correct version number.

Please wait until over a month has passed since the last update before requesting version bumps.

Stable urls for beeper - https://download.todesktop.com/2003241lzgn20jd/beeper-$VERSION.AppImage

https://github.com/NixOS/nixpkgs/pull/241992#issuecomment-1656884024

@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.

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.

@shalzz No problem. Feel free to comment if you have any other issues.

Ah, makes sense. I wasn't aware of the desktop file persistent across upgrades via ~/.local/share/applications. Thanks!

I'm inclined to leave the .desktop file alone because users can already create customized copies in ~/.local/share/applications.

@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!

Btw, I had the same experience with the frame option. Forgot to reply to that message. Didn't seem a good default.

@xiota: tried with yay after a similar thought with makepkg.ill add the epoch in a little bit.