Search
SailfishOS Open Build Service
>
Projects
>
home:rcolistete
>
python-vcversioner
> Changes
Log In
Username
Password
Cancel
Overview
Repositories
Revisions
Requests
Users
Advanced
Attributes
Meta
Changes of Revision 5
[-]
[+]
Added
python-vcversioner.spec
@@ -0,0 +1,54 @@ +# +# spec file for package python-vcversioner for Mer, based on OpenSuse version +# + +%define oname vcversioner + +Name: python-%{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 +Source0: %{oname}-%{version}.tar.gz +BuildRequires: python-devel +BuildRequires: python-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. + +%prep +%setup -q -n %{oname}-%{version} + +%build +python setup.py build + +%install +python setup.py install --prefix=%{_prefix} --root=%{buildroot} + +%check +python setup.py test + +%files +%defattr(-,root,root,-) +%doc README.rst +%{python_sitelib}/%{oname}-%{version}-py%{py_ver}.egg-info +%{python_sitelib}/%{oname}.* + +%changelog +* Sun Aug 14 2016 Roberto Colistete Jr. <rcolistete.maemo@gmail.com> - 2.16.0.0 +- vcversioner 2.16.0.0 (12/04/2016) for Mer (14/08/2016) : +- * first release.