Greetings,

I suggest you actually examine the PKGBUILD before submitting deletion requests. To address your point, there isn't a standalone Python version '311' either; it's a reference to Python 3.11, which exists in the AUR and is quite popular. I followed a similar naming convention here, with the proper naming specified in the provides array.

The idea of merging all dependencies into a single PKGBUILD, simply because it’s possible, is impractical—and I trust I don’t need to explain why. This is especially true for older source trees that may require future patches.

The fact that a package currently has only one dependent, just a few days after being uploaded, doesn’t invalidate its existence. Many packages exist without any dependents and are still valuable. My package serves a purpose, and bundling multiple packages into a single one (like cutter-test) is impractical. Furthermore, removing cutter-test would be unreasonable, given the number of packages that depend on it. I am actively reaching out to other maintainers to integrate testing with cutter-test.

Best regards,
Vitalii