Name:           python-django-evolution
Version:        0.7.2
Release:        %mkrel 1
Summary:        Schema evolution for Django

Group:          Development/Python
License:        BSD
URL:            http://code.google.com/p/django-evolution/
# svn export -%{alphatag} http://django-evolution.googlecode.com/svn/trunk/ django-evolution-%{alphatag}
# tar zcf django-evolution-%{alphatag}.tar.gz django-evolution-%{alphatag}
#Source0:        %{realname}-%{alphatag}.tar.gz
Source0:        http://downloads.reviewboard.org/releases/django-evolution/0.7/django_evolution-%{version}.tar.gz
# Patches from Fedora
Patch0001: FED01-Disable-ez_setup-when-installing-by-RPM.patch



BuildArch:      noarch
BuildRequires:  pkgconfig(python)
BuildRequires:  python-setuptools
BuildRequires:  python-nose
BuildRequires:  python-coverage
BuildRequires:  pyflakes
BuildRequires:  python-sqlite
BuildRequires:  python-django
Requires:       python-django

%description
When you run ./manage.py syncdb, Django will look for any new models that
have been defined, and add a database table to represent those new models.
However, if you make a change to an existing model, ./manage.py syncdb will
not make any changes to the database.

This is where Django Evolution fits in. Django Evolution is an extension to
Django that allows you to track changes in your models over time, and to
update the database to reflect those changes.

%prep
%setup -q -n django_evolution-%{version}
%patch0001 -p1

%build
%{__python} setup.py build

%install
%{__python} setup.py install -O1 --skip-build --root $RPM_BUILD_ROOT
# Delete tests. They aren't useful in an installed system
rm -rf $RPM_BUILD_ROOT/%{python_sitelib}/tests

%check
%{__python} tests/runtests.py
%{__python} tests/run-pyflakes.py

%files
%doc AUTHORS LICENSE README docs/
%{python_sitelib}/django_evolution/*
%{python_sitelib}/django_evolution-%{version}*.egg-info