Hello,
As I said, this is mostly a "style" choice, it is up to the maintainer to adopt the use of such variables or not.
Some prefer using them /(like I do, because I tend to find that it makes the PKGBUILD more "portable" as you can keep the same structure for another package by just modifying the top variables' value)/ and some don't /(as it could be redundant and it eventually makes some information more difficult to read at first glance) /but, as far as I know, there's no real stated rule about this (please, someone correct me if I'm wrong about that).
So once again, I think this is up to you. If you also think that using such variables is redundant, you don't have to use them ;)
This is going to sound very autistic but I like the structure of using variables to substitute in the name of the package, I only removed it because T.J is a TU and I took his advice as the conventional approach.
By the way, I wasn't aware of T.J.'s recommandations since they don't seem to appear in this discussion thread?
Ah, I forgot to mention he emailed me off-list, but he provided some suggestions and diff's for helping the solution. Thank you for the support, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev