Since the SVN revision is now included in %{version}, it's redundant
authormej <mej@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Thu, 16 Jun 2011 20:36:43 +0000 (20:36 +0000)
committermej <mej@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Thu, 16 Jun 2011 20:36:43 +0000 (20:36 +0000)
commit6530c32ae91b3dce64d4b8ebf077e7ed51e6e1dc
treea30fb78d9f415622f1cfafb33f333c26c1c0e7a6
parent527e13ff5515be5a6d28b28addbe83387eae986f
Since the SVN revision is now included in %{version}, it's redundant
to have it in %{release} also.  So let's just tag the package as ours
and try to make sure it doesn't interfere with vendor releases.

git-svn-id: svn+ssh://svn.enlightenment.org/var/svn/e/trunk/evas@60407 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33
evas.spec.in