On Tuesday 27 July 2004 02:38, Michael Jennings wrote:
> On Monday, 26 July 2004, at 23:26:25 (+0200),
>
> Andreas Volz wrote:
> > And if the the questioner has a RPM based distribution you could
> > perhaps use gentoo's feature to create RPM's with ebuild. I wonder
> > why nobody yet uses this feature from gentoo to create (unofficial)
> > RPM packages from E17 CVS?
>
> Because the resulting packages would be completely useless.  There's a
> reason you can't necessarily use FC2 RPM's on a RH9 box and vice
> versa.  Gentoo, Debian, and any other system capable of producing
> RPM's has the same problem.
>
> The spec files for all the EFL libs are clean and working.  RPM's are
> easy to build, no Gentoo required.

I really appriciate the effort of supplying valid spec files in the CVS - its 
make life so much easier for distributions and other packagers. I wish that 
more projects will follow.

I'm trying to build RPMs from CVS for my system (Mandrake 10). actually - 
I'm writing a script that will allow to build E17 CVS and install it as RPMs 
directly. the resulting RPMs will of course be useless for anyone not using 
Mandrake 10, but the source RPMs generated will be useful to build the 
specific CVS snapshot on other systems - much more so then checking out of 
CVS would ever be.

Now - I'm having some problems with doing so, which makes me think your last 
decleration may not be so true (especially the "easy" part). specificly I'm 
currently stuck with these problems, and I do hope someone can comment on how 
I can resolve this issues:

- edje: autogen.sh does not work. the autogen.sh script looks nothing like the 
scripts for the other libraries, and bash complains about all the curly 
braces in the checks in the front. I can't tell what the problem as I'm not 
familiar with this syntax - I don't even think its valid bash. The m4 
directory is also missing.
- imlib2 does not build - it fails finding any files for the imlib-loader_gif 
sub-package.
- imlib2_loaders does not have a spec file - it has a spec.in file. is the 
spec file supposed to be generated by the configure scripts ? that's kind of 
useless as configure is supposed to be run from the spec file.
- I failed to build etox, but I don't think its RPM specific. I'll investigate 
more and write about it later.

Also, issues general to all the libraries:
- In all the libraries, autogen.sh by deafult runs configure (while the 
comment above it implies that it is commented out, which is not the case). as 
the order of building RPMs (AFAIU) is - autogen, rpmbuild (which runs 
configure, make and make install), that step is redundant. I currently solve 
this by automaticly "fixing" the autogen.sh script in my build process.
- All the spec files are missing BuildRequires tags that are needed to force a 
build order - other wise users can try to build packages out of order and 
fail. the BuildRequires tag is supposed to help users by letting them know 
what they need before spending a lot of times (sometimes a couple of hours) 
on a build that would fail.

I haven't tried to compile all the libraries as I got stuck on imlib2 and edje 
which most other libs depend on. 

-- 
Oded 

::..
X windows:
        Putting new limits on productivity.


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
enlightenment-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to