Since version 1.4.1 upstream has used setuptools-scm to determine the
current version number. Unfortunately the package in question does not
support GitHub release archives, using GitHub VCS snapshots would require
retrieving and updating commit hashes corresponding to release tags, and
PyPI tarballs do not contain tests. setuptools_scm_git_archive does not
help because it requires extra files to be included in the repository,
which upstream has not done.

Seeing as we already know the version number, bypass setuptools_scm
altogether and create the version file ourselves. For obvious reasons the
latter has to be done in ebuilds themselves.

--- a/setup.py
+++ b/setup.py
@@ -16,9 +16,6 @@
 
 setup(
     name="protontricks",
-    use_scm_version={
-        "write_to": "src/protontricks/_version.py"
-    },
     description=DESCRIPTION,
     long_description=LONG_DESCRIPTION,
     author=AUTHOR,
@@ -28,11 +25,6 @@
     packages=["protontricks"],
     package_data={"": ["LICENSE"]},
     package_dir={"protontricks": "src/protontricks"},
-    setup_requires=[
-        # setuptools-scm v6 requires Python 3.6+
-        "setuptools_scm<6 ; python_version <= '3.5'",
-        "setuptools_scm ; python_version > '3.5'"
-    ],
     install_requires=["vdf>=3.2"],
     entry_points={
         "console_scripts": [