Hi,
I've tried to use E17, but it's an old version. I've asked e17 team,
and they answered me that E17 is "rolling release". So no
stable release (or vert vert few).
I propose to package svn version, so we could be up-to-date.
If a problem occurs, we could report it to upstream.
I've started such change, for example on eina, the change is :
Index: SPECS/eina.spec
===================================================================
--- SPECS/eina.spec (révision 151537)
+++ SPECS/eina.spec (copie de travail)
@@ -1,14 +1,15 @@
%define major 1
%define libname %mklibname %{name} %major
%define libnamedev %mklibname %{name} -d
+%define svn r64257
Summary: Data Type Library
Name: eina
-Version: 1.0.1
-Release: %mkrel 2
+Version: 1.1.0
+Release: %mkrel 0.%svn.1
License: LGPLv2+
Group: Graphical desktop/Enlightenment
-Source: http://download.enlightenment.org/releases/%{name}-%{version}.tar.bz2
+Source: http://download.enlightenment.org/releases/%{name}-%{svn}.tar.bz2
URL: http://www.enlightenment.org/
%description
@@ -32,9 +33,10 @@
%{name} development headers and libraries.
%prep
-%setup -qn %{name}-%{version}
+%setup -qn %{name}
%build
+sh autogen.sh
%configure2_5x
%make
What do you think about doing it on all E17 package ?
regards,
trem
