@xiota "Unified Messenger" is nice! Yup, you could change the description as well :)
Search Criteria
Package Details: beeper-latest-bin 3.109.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: | A unified messaging app |
Upstream URL: | https://beeper.com/ |
Licenses: | LicenseRef-beeper |
Conflicts: | beeper |
Provides: | beeper |
Submitter: | xiota |
Maintainer: | xiota (sundbp) |
Last Packager: | xiota |
Votes: | 7 |
Popularity: | 0.79 |
First Submitted: | 2023-07-28 06:12 (UTC) |
Last Updated: | 2024-09-29 08:24 (UTC) |
Dependencies (2)
Required by (0)
Sources (1)
gdamms commented on 2024-07-13 10:06 (UTC)
xiota commented on 2024-07-13 06:51 (UTC) (edited on 2024-07-13 06:52 (UTC) by xiota)
@gdamms The .desktop
file has:
Comment=Beeper: Unified Messenger
Which would you prefer for generic name: "Chats", "Unified Messenger", "Messenger", ...?
I'm thinking about changing the description to something like, "A unified messaging application".
gdamms commented on 2024-07-13 06:06 (UTC) (edited on 2024-07-13 06:06 (UTC) by gdamms)
@xiota one of those?
- All your chats in one app
- All chats in one app
- One app, all chats
- All chats
- Chats
Personally, I prefer short generic names.
xiota commented on 2024-07-12 22:59 (UTC)
@gdamms What generic name do you propose?
gdamms commented on 2024-07-12 07:51 (UTC)
Hi! Could you add a GenericName
attribute to the [Desktop Entry]
in the beeper.desktop
file? It would make it pretier and more consistent with other applications in application launchers.
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.
- Or edit
_install_path=usr/lib
– Use a different install path. Default isopt
. (Do not include leading/
and trailing/beeper
.)
joeleg commented on 2024-05-04 16:39 (UTC)
The pkgver function is returning an invalid version at the moment, being the full name of the beeper appimage. Can we change the filtering so that this gets fixed? Thanks
nemonein commented on 2024-05-02 13:26 (UTC) (edited on 2024-05-02 13:30 (UTC) by nemonein)
I had been using AppImage(from beeper.com/download) itself, but it stopped working(only grey window) from this afternoon. I reported this to Beeper, but they do not understand what the problem is. The one I talked to on Beeper.com, might not know what AppImage is. He or she told me to reinstall Beeper Desktop. (How do I REINSTALL the AppImage?)
After that, I've found this AUR package, then tried makepkg. However, it was the same.
Then, I tried _system_electron=true makepkg
, problem solved. Beeper is back!
Thank you guys!
xiota commented on 2024-04-18 09:50 (UTC)
I don't have Nvidia GPU, but tried with LTS kernel and awesome wm with no crash.
Switched to the prepackaged electron. People who prefer the system electron can make this with: _system_electron=true makepkg
v3d commented on 2024-04-18 09:28 (UTC) (edited on 2024-04-18 09:28 (UTC) by v3d)
@xiota
kernel: 6.6.28-1-lts X11 with awesomevm (with sddm) nvidia-lts on 1060 Ti i5-8600K CPU
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)/usr/bin/beeper
after install._install_path=usr/lib
– Use a different install path. Default isopt
. (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.