Update Request: beeper 3.110.1 → 4.0.623

[zh4ngx]

Nixpkgs version

• Unstable (25.05)

Package name

beeper

Upstream version

4.0.623

Nixpkgs version

3.110.1

Changelog

https://beeper.notion.site/

Notify maintainers

@jshcmpbll @mjm @edmundmiller

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this package update does not yet exist in an open pull request or in Nixpkgs Unstable.
• I assert that this is not a duplicate of any known issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[zh4ngx]

I can give this a shot. FYI the new beeper download links moved:

$ curl https://api.beeper.com/desktop/download/linux/x64/stable/com.automattic.beeper.desktop
Found. Redirecting to https://beeper-desktop.download.beeper.com/builds/Beeper-4.0.570.AppImage

[zh4ngx]

Gave this a try and had some trouble getting the desktop entry working. Only a single "0x0" folder exists - any thoughts on the best way to handle?

[ymstnt]

I've packaged the new Beeper in NUR and I too ran into some trouble with the desktop entry.
Here is how I did it: https://github.com/ymstnt/nur-packages/blob/master/pkgs/beeper/default.nix

(Since then Beeper fixed the 0x0 thing at least)

Also, Beeper 4.0.584 is out.

[zh4ngx]

I've packaged the new Beeper in NUR and I too ran into some trouble with the desktop entry. Here is how I did it: https://github.com/ymstnt/nur-packages/blob/master/pkgs/beeper/default.nix

(Since then Beeper fixed the 0x0 thing at least)

Also, Beeper 4.0.584 is out.

Thanks for the tips! I had tried switching the pname to "beepertexts" but maybe that was causing the problem. So the bin file is "beeper" as well, and only the .desktop file is name "beepertexts" ?

[ymstnt]

Thanks for the tips! I had tried switching the pname to "beepertexts" but maybe that was causing the problem. So the bin file is "beeper" as well, and only the .desktop file is name "beepertexts" ?

Yes, that would be correct. My guess is that since the Automattic acquisition Beeper has started making the new desktop app using code from Texts.com, thus the name "beepertexts". However, it is probably just an internal name for this new desktop app, probably so they could differentiate the legacy Beeper app forked from Element from this one, that's why the binary stayed "beeper", I guess.

That being said, the legacy apps seem to be gone from their download page. I wonder if this is because they're now considered stable, which is weird, since there was a blog post in February announcing the "beta version of the next-generation of desktop apps".
In any case, I didn't bother touching the updater-script part, so don't copy that from my package, they're still pointing to the legacy client.

Everything else seems to be working correctly, I've been using the new client this way since a few months without any problems whatsoever.

[zh4ngx]

Thanks for sharing and explaining. Yes, I did read that the desktop app was based off of the Texts.com base, that didn't fully register until now. IIRC, the version (4.0.522) I originally tried to build on nix actually had a renamed binary (beepertexts), which is probably why I just changed the pname altogether. Your approach makes more sense.

Do you know how the updater script is supposed to be used? My guess is it's a shell script that's exposed to the executable when you click "Check for updates" - is that right?

[zh4ngx]

Another question - can you explain the postExtract script?

When you say # disable creating a desktop file and icon in the home folder during runtime do you mean that the appImage would actually try to create a desktop file every time?