Yeah, this should become vpkedit-git and be pinned to specific tags/commits for versioning

Hi. It seems like this package uses a few libraries that are fetched via their very last git commits. I think this might cause a few issues? (though I may be wrong, I'm not too knowledgeable in AUR packaging)

• The PKGBUILD is definitely not reproducible. If a computer has a specific version installed, and another computer has the SAME exact version installed, depending on the time of compilation, they could still differ because of some of the sources having received a few additional commits (imo this isn't acceptable if this isn't a -git package).
• I assume some AUR helpers will attempt to recompile the entire package whenever one of the dependencies have a new commit? On my end (via paru), it alerts me that I can upgrade the package a LOT of times (despite there not actually being a new vpkedit version available). Most of the times, the compile process seems to skip compilation and it ends up just reinstalling the package I had previously installed. I'm not sure what it is doing there.

I think it could work if you were to assign specific tags or commits for every git sources there are specifically to avoid all this.

Also, the sourcepp repo uses doxygen-awesome-css as a submodule, but it seems like that one isn't actually necessary for vpkedit, since it is just there to add stylesheets to the sourcecpp docs which doesn't get shipped with vpkedit?