current/SPECS/python-django-evolution.spec

%define alphatag r212
%define realname django-evolution

Name:           python-django-evolution
Version:        0.6.7
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://pypi.python.org/packages/source/d/django_evolution/django_evolution-%{version}.tar.gz
# Patches from Fedora
Patch0001: FED01-Disable-ez_setup-when-installing-by-RPM.patch


BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-buildroot

BuildArch:      noarch
BuildRequires:  python-devel
BuildRequires:  python-setuptools
BuildRequires:  python-nose
BuildRequires:  python-coverage
BuildRequires:  pyflakes
BuildRequires:  python-sqlite
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 %{realname}-%{version}
%patch0001 -p1

%build
%{__python} setup.py build

%install
%{__python} setup.py install -O1 --skip-build --root $RPM_BUILD_ROOT

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

%files
%doc AUTHORS LICENSE README docs/
%{py_puresitedir}/*


1	%define alphatag r212
2	%define realname django-evolution
3
4	Name: python-django-evolution
5	Version: 0.6.7
6	Release: %mkrel 1
7	Summary: Schema evolution for Django
8
9	Group: Development/Python
10	License: BSD
11	URL: http://code.google.com/p/django-evolution/
12	# svn export -%{alphatag} http://django-evolution.googlecode.com/svn/trunk/ django-evolution-%{alphatag}
13	# tar zcf django-evolution-%{alphatag}.tar.gz django-evolution-%{alphatag}
14	#Source0: %{realname}-%{alphatag}.tar.gz
15	Source0: http://pypi.python.org/packages/source/d/django_evolution/django_evolution-%{version}.tar.gz
16	# Patches from Fedora
17	Patch0001: FED01-Disable-ez_setup-when-installing-by-RPM.patch
18
19
20	BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot
21
22	BuildArch: noarch
23	BuildRequires: python-devel
24	BuildRequires: python-setuptools
25	BuildRequires: python-nose
26	BuildRequires: python-coverage
27	BuildRequires: pyflakes
28	BuildRequires: python-sqlite
29	Requires: python-django
30
31	%description
32	When you run ./manage.py syncdb, Django will look for any new models that
33	have been defined, and add a database table to represent those new models.
34	However, if you make a change to an existing model, ./manage.py syncdb will
35	not make any changes to the database.
36
37	This is where Django Evolution fits in. Django Evolution is an extension to
38	Django that allows you to track changes in your models over time, and to
39	update the database to reflect those changes.
40
41	%prep
42	%setup -q -n %{realname}-%{version}
43	%patch0001 -p1
44
45	%build
46	%{__python} setup.py build
47
48	%install
49	%{__python} setup.py install -O1 --skip-build --root $RPM_BUILD_ROOT
50
51	%check
52	%{__python} tests/runtests.py
53	%{__python} tests/run-pyflakes.py
54
55	%files
56	%doc AUTHORS LICENSE README docs/
57	%{py_puresitedir}/*
58
59