File python3-vcversioner.spec of Package python3-vcversioner

#
# spec file for package python3-vcversioner for Mer, based on OpenSuse version
#

%define oname   vcversioner

Name:           python3-%{oname}
Version:        2.16.0.0
Release:        0
License:        ISC
Packager:       Roberto Colistete Jr. <rcolistete.maemo@gmail.com>
Summary:        Use version control tags to discover version numbers
Url:            https://github.com/habnabit/vcversioner
Group:          Development/Languages/Python
Source:         %{oname}-%{version}.tar.gz
BuildRequires:  python3-devel
# BuildRequires:  python3-setuptools
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildArch:      noarch

%description
Elevator pitch: you can write a "setup.py" with no version information
specified, and vcversioner will find a recent, properly-formatted VCS tag and
extract a version from it.

It's much more convenient to be able to use your version control system's
tagging mechanism to derive a version number than to have to duplicate that
information all over the place. I eventually ended up copy-pasting the same
code into a couple different "setup.py" files just to avoid duplicating
version information. But, copy-pasting is dumb and unit testing "setup.py"
files is hard. This code got factored out into vcversioner.

%define python3_sitelib %{_libdir}/python3.?/site-packages

%prep
%setup -q -n %{oname}-%{version}

%build
python3 setup.py build

%install
python3 setup.py install --prefix=%{_prefix} --root=%{buildroot}

%files
%defattr(-,root,root,-)
%{python3_sitelib}/*
%doc README.rst

%changelog
* Sun Aug 14 2016 Roberto Colistete Jr. <rcolistete.maemo@gmail.com> - 2.16.0.0
- (Python 3) vcversioner 2.16.0.0 (12/04/2016) for Mer (14/08/2016) :
-  * first release.