%global _empty_manifest_terminate_build 0
Name:		python-hgdistver
Version:	0.25
Release:	1
Summary:	obsoleted by setuptools_scm
License:	MIT
URL:		http://bitbucket.org/RonnyPfannschmidt/hgdistver/
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/98/7b/337f0108b7d2236a6c76eadfd457815fb91b0aa637e43c22947fa7f4050c/hgdistver-0.25.tar.gz
BuildArch:	noarch


%description
hgdistver
~~~~~~~~~

.. warning::
  
  this module is superseeded by setuptools_scm

This module is a simple drop-in to support setup.py
in mercurial and git based projects.

Alternatively it can be a setup time requirement.

It extracts the last Tag as well as the distance to it in commits
from the scm, and uses these to calculate a version number

By default, it will increment the last component of the Version by one
and append .dev{distance}
in case the last component is .dev, the version will be unchanged

Tis requires always using all components in tags (i.e. 2.0.0 instead of 2.0)
to avoid misstakenly releasing higher version
(i.e. 2.1.devX instead of 2.0.1.devX)




It uses 4 strategies to archive its task:

1. try to directly ask hg for the tag/distance
2. try to infer it from the `.hg_archival.txt` file
3. try to read the exact version the cache file if it exists
4. try to read the exact version from the 'PKG-INFO' file
   as generated by `setup.py sdists` (this is a nasty abuse)

The most simple usage is::

    from setuptools import setup
    from hgdistver import get_version
    setup(
        ...,
        version=get_version(),
        ...,
    )

`get_version` takes the optional argument `cachefile`,
which causes it to store the version info in a python script instead
of abusing PKG-INFO from a sdist.


The setup requirement usage is::

    from setuptools import setup
    setup(
        ...,
        get_version_from_hg=True,
        setup_requires=['hgdistver'],
        ...,
    )

The requirement uses the setup argument cache_hg_version_to instead of cachefile.

%package -n python3-hgdistver
Summary:	obsoleted by setuptools_scm
Provides:	python-hgdistver
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-hgdistver
hgdistver
~~~~~~~~~

.. warning::
  
  this module is superseeded by setuptools_scm

This module is a simple drop-in to support setup.py
in mercurial and git based projects.

Alternatively it can be a setup time requirement.

It extracts the last Tag as well as the distance to it in commits
from the scm, and uses these to calculate a version number

By default, it will increment the last component of the Version by one
and append .dev{distance}
in case the last component is .dev, the version will be unchanged

Tis requires always using all components in tags (i.e. 2.0.0 instead of 2.0)
to avoid misstakenly releasing higher version
(i.e. 2.1.devX instead of 2.0.1.devX)




It uses 4 strategies to archive its task:

1. try to directly ask hg for the tag/distance
2. try to infer it from the `.hg_archival.txt` file
3. try to read the exact version the cache file if it exists
4. try to read the exact version from the 'PKG-INFO' file
   as generated by `setup.py sdists` (this is a nasty abuse)

The most simple usage is::

    from setuptools import setup
    from hgdistver import get_version
    setup(
        ...,
        version=get_version(),
        ...,
    )

`get_version` takes the optional argument `cachefile`,
which causes it to store the version info in a python script instead
of abusing PKG-INFO from a sdist.


The setup requirement usage is::

    from setuptools import setup
    setup(
        ...,
        get_version_from_hg=True,
        setup_requires=['hgdistver'],
        ...,
    )

The requirement uses the setup argument cache_hg_version_to instead of cachefile.

%package help
Summary:	Development documents and examples for hgdistver
Provides:	python3-hgdistver-doc
%description help
hgdistver
~~~~~~~~~

.. warning::
  
  this module is superseeded by setuptools_scm

This module is a simple drop-in to support setup.py
in mercurial and git based projects.

Alternatively it can be a setup time requirement.

It extracts the last Tag as well as the distance to it in commits
from the scm, and uses these to calculate a version number

By default, it will increment the last component of the Version by one
and append .dev{distance}
in case the last component is .dev, the version will be unchanged

Tis requires always using all components in tags (i.e. 2.0.0 instead of 2.0)
to avoid misstakenly releasing higher version
(i.e. 2.1.devX instead of 2.0.1.devX)




It uses 4 strategies to archive its task:

1. try to directly ask hg for the tag/distance
2. try to infer it from the `.hg_archival.txt` file
3. try to read the exact version the cache file if it exists
4. try to read the exact version from the 'PKG-INFO' file
   as generated by `setup.py sdists` (this is a nasty abuse)

The most simple usage is::

    from setuptools import setup
    from hgdistver import get_version
    setup(
        ...,
        version=get_version(),
        ...,
    )

`get_version` takes the optional argument `cachefile`,
which causes it to store the version info in a python script instead
of abusing PKG-INFO from a sdist.


The setup requirement usage is::

    from setuptools import setup
    setup(
        ...,
        get_version_from_hg=True,
        setup_requires=['hgdistver'],
        ...,
    )

The requirement uses the setup argument cache_hg_version_to instead of cachefile.

%prep
%autosetup -n hgdistver-0.25

%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-hgdistver -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Fri Apr 21 2023 Python_Bot <Python_Bot@openeuler.org> - 0.25-1
- Package Spec generated