%global _empty_manifest_terminate_build 0 Name: python-versioningit Version: 2.2.0 Release: 1 Summary: Versioning It with your Version In Git License: MIT URL: https://github.com/jwodder/versioningit Source0: https://mirrors.nju.edu.cn/pypi/web/packages/60/84/f547ab132f18f063a782b6f5b58e1c732725e0c10f63ab3a37691f61ed2a/versioningit-2.2.0.tar.gz BuildArch: noarch Requires: python3-packaging Requires: python3-importlib-metadata Requires: python3-tomli %description ``versioningit`` requires Python 3.7 or higher. Just use `pip `_ for Python 3 (You have pip, right?) to install ``versioningit`` and its dependencies:: python3 -m pip install versioningit However, usually you won't need to install ``versioningit`` in your environment directly. Instead, you specify it in your project's ``pyproject.toml`` file in the ``build-system.requires`` key, like so: [build-system] requires = [ "setuptools >= 42", # At least v42 of setuptools required! "versioningit", ] build-backend = "setuptools.build_meta" Then, you configure ``versioningit`` by adding a ``[tool.versioningit]`` table to your ``pyproject.toml``. See `the documentation`__ for details, but you can get up & running with just the minimal configuration, an empty table: __ https://versioningit.readthedocs.io/en/stable/configuration.html [tool.versioningit] ``versioningit`` replaces the need for (and will overwrite) the ``version`` keyword to the ``setup()`` function, so you should remove any such keyword from your ``setup.py``/``setup.cfg`` to reduce confusion. **Note:** If you're using setuptools' recent support for specifying project metadata in ``pyproject.toml``, you need to omit the ``project.version`` key and set ``project.dynamic = ["version"]`` in order for ``versioningit`` to work. Once you have a ``[tool.versioningit]`` table in your ``pyproject.toml`` — and once your repository has at least one tag — building your project with ``setuptools`` while ``versioningit`` is installed (which happens automatically if you set up your ``build-system.requires`` as above and you're using a automatically being set based on the latest tag in your Git repository. You can test your configuration and see what the resulting version will be using the ``versioningit`` command (`see the documentation`__). __ https://versioningit.readthedocs.io/en/stable/command.html %package -n python3-versioningit Summary: Versioning It with your Version In Git Provides: python-versioningit BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-versioningit ``versioningit`` requires Python 3.7 or higher. Just use `pip `_ for Python 3 (You have pip, right?) to install ``versioningit`` and its dependencies:: python3 -m pip install versioningit However, usually you won't need to install ``versioningit`` in your environment directly. Instead, you specify it in your project's ``pyproject.toml`` file in the ``build-system.requires`` key, like so: [build-system] requires = [ "setuptools >= 42", # At least v42 of setuptools required! "versioningit", ] build-backend = "setuptools.build_meta" Then, you configure ``versioningit`` by adding a ``[tool.versioningit]`` table to your ``pyproject.toml``. See `the documentation`__ for details, but you can get up & running with just the minimal configuration, an empty table: __ https://versioningit.readthedocs.io/en/stable/configuration.html [tool.versioningit] ``versioningit`` replaces the need for (and will overwrite) the ``version`` keyword to the ``setup()`` function, so you should remove any such keyword from your ``setup.py``/``setup.cfg`` to reduce confusion. **Note:** If you're using setuptools' recent support for specifying project metadata in ``pyproject.toml``, you need to omit the ``project.version`` key and set ``project.dynamic = ["version"]`` in order for ``versioningit`` to work. Once you have a ``[tool.versioningit]`` table in your ``pyproject.toml`` — and once your repository has at least one tag — building your project with ``setuptools`` while ``versioningit`` is installed (which happens automatically if you set up your ``build-system.requires`` as above and you're using a automatically being set based on the latest tag in your Git repository. You can test your configuration and see what the resulting version will be using the ``versioningit`` command (`see the documentation`__). __ https://versioningit.readthedocs.io/en/stable/command.html %package help Summary: Development documents and examples for versioningit Provides: python3-versioningit-doc %description help ``versioningit`` requires Python 3.7 or higher. Just use `pip `_ for Python 3 (You have pip, right?) to install ``versioningit`` and its dependencies:: python3 -m pip install versioningit However, usually you won't need to install ``versioningit`` in your environment directly. Instead, you specify it in your project's ``pyproject.toml`` file in the ``build-system.requires`` key, like so: [build-system] requires = [ "setuptools >= 42", # At least v42 of setuptools required! "versioningit", ] build-backend = "setuptools.build_meta" Then, you configure ``versioningit`` by adding a ``[tool.versioningit]`` table to your ``pyproject.toml``. See `the documentation`__ for details, but you can get up & running with just the minimal configuration, an empty table: __ https://versioningit.readthedocs.io/en/stable/configuration.html [tool.versioningit] ``versioningit`` replaces the need for (and will overwrite) the ``version`` keyword to the ``setup()`` function, so you should remove any such keyword from your ``setup.py``/``setup.cfg`` to reduce confusion. **Note:** If you're using setuptools' recent support for specifying project metadata in ``pyproject.toml``, you need to omit the ``project.version`` key and set ``project.dynamic = ["version"]`` in order for ``versioningit`` to work. Once you have a ``[tool.versioningit]`` table in your ``pyproject.toml`` — and once your repository has at least one tag — building your project with ``setuptools`` while ``versioningit`` is installed (which happens automatically if you set up your ``build-system.requires`` as above and you're using a automatically being set based on the latest tag in your Git repository. You can test your configuration and see what the resulting version will be using the ``versioningit`` command (`see the documentation`__). __ https://versioningit.readthedocs.io/en/stable/command.html %prep %autosetup -n versioningit-2.2.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-versioningit -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Tue May 30 2023 Python_Bot - 2.2.0-1 - Package Spec generated