Package Details: beeper-latest-bin 3.104.7-1

Git Clone URL: https://aur.archlinux.org/beeper-latest-bin.git (read-only, click to copy)
Package Base: beeper-latest-bin
Description: all your chats in one app
Upstream URL: https://beeper.com/
Licenses: LicenseRef-beeper
Conflicts: beeper
Provides: beeper
Submitter: xiota
Maintainer: xiota (sundbp)
Last Packager: xiota
Votes: 6
Popularity: 0.095003
First Submitted: 2023-07-28 06:12 (UTC)
Last Updated: 2024-05-05 02:31 (UTC)

Pinned Comments

xiota commented on 2024-05-05 02:26 (UTC) (edited on 2024-05-05 02:33 (UTC) by xiota)

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

xiota commented on 2023-07-28 06:41 (UTC) (edited on 2024-02-29 23:18 (UTC) by xiota)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

hollandheese commented on 2023-10-05 16:11 (UTC)

pkgver is broken for the latest beeper.

Getting:

pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: beeper-3.79.17-build-231004eglj00sp6.AppImage

sundbp commented on 2023-08-25 09:02 (UTC)

Agreed. Just submitted a Merge request.

xiota commented on 2023-08-04 06:42 (UTC) (edited on 2023-10-06 01:08 (UTC) by xiota)

@jshcmpbll As far as I can tell, that is not an official url. I'll use it to add support for building old versions.

Note: Rebuilding old versions may no longer work with 3.79.17 and newer because upstsream changed the filename format.

jshcmpbll commented on 2023-08-03 21:11 (UTC)

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

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

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!

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »