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)
commit2116f991b9a0da0fad849519bdb443581a7d2a12
tree19784f785d1819050c7f0739f0ecabf50624f55c
parente4ee91dbdfe1496d158545f2ed804046feb43f25
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/ecore@60407 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33
ecore.spec.in