Package Details: eden-beta 0.0.4.rc3-2

Git Clone URL: https://aur.archlinux.org/eden-beta.git (read-only, click to copy)
Package Base: eden-beta
Description: Nintendo Switch emulator forked from yuzu - beta and test releases
Upstream URL: https://eden-emulator.github.io/
Licenses: GPL-3.0-or-later
Conflicts: eden, eden-bin, eden-git, eden-preview-bin
Provides: eden
Submitter: username227
Maintainer: username227
Last Packager: username227
Votes: 0
Popularity: 0.000000
First Submitted: 2025-10-27 21:25 (UTC)
Last Updated: 2025-11-22 23:16 (UTC)

Latest Comments

crueter commented on 2025-11-19 21:01 (UTC)

Alright. Going forward, I will leave all test tags intact and put any new ones we create into branches.

username227 commented on 2025-11-19 20:57 (UTC)

I assume it's theoretically possible, but i'd have to research. it's possible that an AUR expert might have the answer. I do know that it is easy enough to differentiate between annotated and unannotated tags. If, for example, all test tags were unannotated, and all regular tags were annotated, we could have it ignore the unannotated tags. there may be a way to to alter this somehow to exclude tags with certain words but it wouldn't be built into the command so we'd need to figure out a different way.But yes, I can also confirm that if the test tags are in a separate branch, they will still show up on the list of tags, but they will not trigger a recount in the AUR - this happened once before also, much to my confusion until I realized the reason.

crueter commented on 2025-11-19 20:53 (UTC)

All test tags will have test in the name. Is there any way you can exclude those from the pkgver function? If so, that's the ideal solution, unless we create separate branches for test tags going forward... which may not be a bad idea

username227 commented on 2025-11-19 20:52 (UTC)

OK will do. thanks for the info. While we're on the subject of tags - on the git package, it identifies test tags and restarts the count of the pkgver based on the new tag. If that tag is then deleted, people are prone to stop receiving the git updates as AU helpers could mistakenly think it's a downgrade. This actually did happen once last month. The only way around this that I can think of is to go back to commit numbers and remove tag info from the pkgver completely, unless you can think of a better way.

crueter commented on 2025-11-19 20:28 (UTC)

FYI: test tags are volatile and prone to being deleted at any point. I would recommend sticking with direct tagged releases, NOT test tags. We use them to test our CI.

SpicerXD commented on 2025-11-01 18:05 (UTC)

fmt, enet, and cubeb are additional required dependencies for this package.