The variable they recommended was build_id
but that didn't create a clean
makepkg --printsrcinfo > .SRCINFO
Here are some of the comments, it's like
https://aur.archlinux.org/packages/motivewave#comment-932313
https://aur.archlinux.org/packages/motivewave#comment-932245
https://aur.archlinux.org/packages/motivewave#comment-932340
https://aur.archlinux.org/packages/motivewave#comment-932245
https://aur.archlinux.org/packages/motivewave#comment-932340
Xiota also manages chaotic AUR, so he created an 'issue' where two packages
wouldn't be able to exist, so he deleted motivewave and created
motivewave-latest-bin
Then I got re-uploaded, and within hours he re-deleted me again.
He also blocked me from their Git.
Then he moved again to AUR motivewave to team up and the comments started
again.
I would like to know what the rules are, today at Labor Day 3 AM the change
requests arrive again, yesterday I had to leave church to come home and do
more changes Test the package, was working.
I don't want to be forced to use variables or have a permanent code
reviewer.
Be called incompetent or imply I am dumb and need help.
This is in the git and shows how their suggestions actually broke the
package.
I created my custom variable
but the nit picking has not continued.
Calling a person non competent, rude, rude, rude.
Especially when today the issue has been resolved.
Here is how the package broke because code review.
commit 1bceb28d1875deb4a303e6f13ee51e1ea86c0011
Author: Xavier Baez