Package Details: cursor-bin 1.1.5-1

Git Clone URL: https://aur.archlinux.org/cursor-bin.git (read-only, click to copy)
Package Base: cursor-bin
Description: Cursor App - AI-first coding environment
Upstream URL: https://www.cursor.com/
Licenses: custom:proprietary
Submitter: g.schulz
Maintainer: g.schulz
Last Packager: g.schulz
Votes: 55
Popularity: 8.29
First Submitted: 2024-06-09 14:27 (UTC)
Last Updated: 2025-06-21 21:05 (UTC)

Pinned Comments

g.schulz commented on 2025-05-17 08:01 (UTC) (edited on 2025-05-18 10:16 (UTC) by g.schulz)

For anyone who want's to contribute a PR, this is the repo: https://github.com/Gunther-Schulz/aur-cursor-bin-updater

Latest Comments

1 2 3 4 5 6 .. 18 Next › Last »

oech3 commented on 2025-06-15 14:11 (UTC)

Submitting duplicated cursor-* pkgs by people would not stopped until upstream fix $ARGV0 issue or stop distributing AppImage. Unfortunately, upstream seems negative to fix it.

vitaliikuzhdin commented on 2025-06-13 10:45 (UTC)

@oech3, it's extremely unrealistic for a highly profitable company to suddenly undercut itself and make this open source. They don't own their own LLMs, so the only thing they can sell is their app.

oech3 commented on 2025-06-13 10:21 (UTC)

I don't like renaming this cursor. Upstream may distribute source code in the future... +1 for

wait for the latest stable release to catch up with the unstable release.

vitaliikuzhdin commented on 2025-06-12 16:50 (UTC)

@oech3, regarding your proposal to add cursor-stable: the assumption for an Arch package is that it builds from a stable source, unless noted otherwise. This means that instead of having cursor and cursor-stable, we should have cursor and cursor-unstable (or some other prefix, like beta). This wouldn't require adding epoch=1 if we simply wait for the latest stable release to catch up with the unstable release. That said, I don't see why using an epoch would be a problem at all. Also, while not critical, the correct name for this package is cursor, not cursor-bin, so if the maintainer ever decides to rename and merge it, they can start with the new page following the stable track without needing an epoch. Previously, the request to merge cursor-bin into cursor was rejected because the former was of lower quality. Now that it's gone, it might be worth reconsidering that change.

oech3 commented on 2025-06-12 03:52 (UTC) (edited on 2025-06-12 06:09 (UTC) by oech3)

Please consider extracting this as cursor-electron. Other packages are no longer avaiable. https://github.com/Gunther-Schulz/aur-cursor-bin-updater/pull/14

oech3 commented on 2025-06-11 18:29 (UTC) (edited on 2025-06-11 18:30 (UTC) by oech3)

@FabioLolix Should I adjust the PR to add _EULA? I edited https://github.com/Gunther-Schulz/aur-cursor-bin-updater/pull/10 to remove post_install.

FabioLolix commented on 2025-06-11 16:40 (UTC)

Hi,

  • please use ${pkgver} in source=() instead of 1.0.1
license=('custom:Proprietary')  # Replace with the correct license if known

license=(LicenseRef-Cursor_EULA), license need to be installed in "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE", see also https://github.com/Gunther-Schulz/aur-cursor-bin-updater/pull/6/files


post_install() {
    update-desktop-database -q
    xdg-icon-resource forceupdate
}

Not needed since already done by pacman hooks, if pre/post install/remove are needed they belong into a .install file not inside the pkgbuild

dsingal commented on 2025-06-08 20:15 (UTC)

was able to build the latest version using paru -Sccc followed by paru -Syyu cursor-bin

g.schulz commented on 2025-06-08 17:47 (UTC)

For anyone who has problem with the hash check, you need to clean-build all packages when running yay. I am assuming two releases with the same version number but different hashes where released and yay will try to use the cached appimage. WHen you choose clean build it will download the current package.

I suspect this happens because currently we package the bleeding edge version. I will switch to the stable version soon to avoid these kind of issues in the future. If there is interest I can add a another PKGBUILD for the bleeding edge version as well.

robindegen commented on 2025-06-08 13:18 (UTC)

Doesn't update anymore since 1.0.1-2 due to AppImage hash check failure