Hi, a package maintainer who also maintains the upstream project means well but bumps the version of their git packages very frequently without a good reason. I've tried to explain that users want to use CVS packages for good reasons and that it's desirable to follow the guidelines regarding version bumps for CVS packages. These well-intentioned version bumps can be very inconvenient for users of many CVS packages. We seem to be talking past each other. Can someone please help to explain why it's not such a great idea to provide git packages with version bumps for the "wrong" reasons?
I'm convinced that the maintainer's intentions are well-meaning. However, I use CVS packages the way they were originally intended, and version bumps like that can be very disruptive. See the comments at https://aur.archlinux.org/packages/gtk-nocsd-git . https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086532 https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086552 https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086555 https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086557 https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086559 https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086560 https://aur.archlinux.org/packages/gtk-nocsd-git#comment-1086561 TIA, Ralf
