search

kernc / xsuspender

:eyes: :computer: :zzz: :battery: Save battery by auto-suspending unfocused X11 applications.
https://kernc.github.io/xsuspender/
Do What The F*ck You Want To Public License
314 stars 19 forks source link

AUR package does not update automatically #35

Open stewi1014 opened 2 years ago

stewi1014 commented 2 years ago

The AUR package I created works properly and follows guidelines, but I wanted to start a discussion on bumping its pkgver (make AUR helpers update it automatically). Currently the package builds from the latest commit and installs, and never updates without the user explicitly re-installing it.

There's some interesting discussion here; https://wiki.archlinux.org/title/Talk:VCS_package_guidelines#Guidelines_on_updating_version_numbers https://wiki.archlinux.org/title/Talk:VCS_package_guidelines#Warn_against_trivial_pkgver_bumps

Notably there doesn't seem to be much consensus on how packagers should handle this. I think the arguments against mostly focus on avoiding bumping it on every commit, which is fair. Bumping on new releases seems more common, and IMHO, a reasonable path to take to make it explicit to the user that it's worth updating.

My proposal would be to implement a pipeline to update the pkgver on the creation of new releases. I can implement this.

What are people's thoughts on this and what do we do for the other packages? Other options are adding a second non '-git' package that follows releases, or leaving it as is and letting updates be the responsibility of users.

stewi1014 commented 1 year ago

@kernc I think I will attempt to create an 'xsuspender' or 'xsuspender-bin' package and have it update through a pipeline.

I'll fork the repo and experiment with github ci and get back to you with what I find.

kernc commented 1 year ago

I'm not familiar with Arch or AUR, but bumping packages on tagged releases (as long as they are prompt and proper 😅) sounds perfectly reasonable. Thanks!