You are not logged in.
Anytype, an offline-first, decentralized, P2P & E2EE notes/mindmapping/everything app platform, has three AUR packages.
Anytype-bin, which downloads and installs an AppImage from their Digital Ocean CDN.
Anytype-electron-bin and Anytype-alpha-bin, both download a .deb package from anyproto/anytype-ts github release. Extract it and move to /opt.
Interestingly, anytype-electron-bin updates the package with most-to-all releases, including when alpha versions come out.
anytype-alpha-bin, has been updated with less frequency, mostly normal release versions.
I have a small aversion to appimage formats, and prefer just the .tar and a desktop file to install stuff.
Simply, Anytype-electron-bin updates too regularly with alpha updates, and anytype-alpha-bin, which would be more suitable for this, doesn't.
But I'd rather not rely on anytype-alpha-bin, because they might change trajectory and begin updating with every alpha-release in the future. However, their general .pkgbuild is good.
Either, both packages start following their namesake, or I propose a new AUR package, which uses the tar.gz, and updates only at each release.
Offline
updates only at each release.
That's the standard for most packages regardless of -bin or built from source.
https://github.com/anyproto/anytype-ts byuild instructions indicate 2 packages will be needed, anytype-heart and anytype-ts .
Try creating a PKGBUILD for anytype-heart , it uses golang so start with reading https://wiki.archlinux.org/title/Go_package_guidelines
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online