On Tue, 2004-07-27 at 18:43, Michael Jennings wrote: > On Tuesday, 27 July 2004, at 03:26:34 (+0300), > Oded Arbel wrote: > > > 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 not so sure I agree. Many software developers do not know how to > make correct spec files. I can't even begin to count the number of > projects I've run into where the spec file was out-of-date, incorrect, > or just plain nasty. I try very hard to make good, clean, portable > spec files, and I've been doing it since around 2000. >
At worst we're no worse off then w/o spec files at all, and we can offer fixes. at best we have less work to do :-) > In fact, for the entirety of EFL (save perhaps > emotion), I can build RPM's by running the following in each > directory: > > ./autogen.sh && make dist && mzbuild > > The "mzbuild" command is part of Mezzanine (http://www.kainx.org/mezzanine/) > and makes lots of things about building and maintaining packages a > *lot* simpler. If you don't have mezz and don't want to use it, this > will do something quite similar to "mzbuild" in the above command: > > rpmbuild -ba --define "_sourcedir $PWD" --define "_specdir $PWD" \ > --define "_topdir $PWD" --define "%_srcrpmdir $PWD" \ > --define "_rpmdir $PWD" That's mighty useful, I didn't know about that. I still think that SRPMS are more useful then CVS for building distribution packages as they are less steps involved. specificly there are people who don't know a thing about CVS but can manage a simple rebuild command. > > - edje: autogen.sh does not work. > > It works quite well for me as of 3 days ago, so I'd be surprised if > it's not valid bash. More likely a problem with your distro. > Mandrake is notorious for instability. Please don't go mud-slinging. I've been using Mandrake for over 5 years w/o major problems and in the last couple of years w/o any problem. I can say the same for almost any distro you choose (excluding of course RedHat 6.x and distro with the same outdated software, i.e. debian latest stable), but I won't. It was a problem with my script. I'm sorry I didn't found it earlier. it modified autogen.sh and didn't do it correctly. sorry for bothering. > > - imlib2 does not build - it fails finding any files for the imlib-loader_gif > > sub-package. > > Probably because you don't have libungif-devel installed. Thanks - that did the trick. can you please add libungif-devel as BuildRequires for the imlib2 spec file ? > > - 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. > > This must've been an oversight on my part. The spec file I use can be > found via CVS at :pserver:[EMAIL PROTECTED]:/var/cvs in > caos/users/mej/imlib2_loaders/F/imlib2_loaders.spec Thanks. is it possible that it be put in the e17 CVS like the rest of the spec files ? > > - I failed to build etox, but I don't think its RPM specific. I'll investigate > > more and write about it later. > > Building RPM's from CVS still means that you need all the prereq's. > Although if you use Mezzanine and set your hint-installer variable to > "yum -ty install" it will auto-install all buildreq's for you. I don't use Messaine and I don't use yum (I have used it several times, including as recent as FC2, and I still think urpmi is way better). see below. > > - 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). > > autogen.sh is needed to generate the configure script and other such > tools. .. you can simply run "make dist" followed by > rpmbuild/mzbuild. I thought that I can make a dist ball just by running the auto-tools, and packaging the CVS directory after that. can you please explain what's wrong with this approach ? The problem I'm having (IMHO anyway - it may all be just in my mind) is that running configured/make and friends changes a lot of files in the CVS dir, and thus making the next build only as clean as make distclean can make it - which is as usall an error-prone process. I rather build stuff out of as clean as dist as possible, with the least ammounts of steps that can go wrong. I think that packaging the CVS dir as it comes out of the CVS and building off that is the ultimate goal and I sometimes do that. > The problem with BuildRequires is that they aren't distro-portable. > And because missing BuildRequires are fatal (rpmbuild will die without > them, even if they're not strictly needed), There are ways to add BuildRequires in a way that is not (or at least - as little as possible) distribution dependant. there are efforts to solve the last remaining cross distribution dependency problems. I don't think its fair to assume that just because something was broken in the past it will always and forever be broken (see Mandrake comment above). Also, if you try to build something and BuildRequires complain about something that you know you have, then there's always --nodeps. I know its not a good idea, but its useful as sometimes you put in stuff not through the package manager and then use it in builds. > Your problem seems to be related more to Mandrake 10 than to E. :) Oh, come on. this is not fair. I can just as well say that my problem is you using non-standard tools in an undocumented way and expecting people to magically know that and use them (I actually grepped the CVS tree for "mezzanine" and failed to find any reference). Thanks for the response, and I am sorry if I hurt anyone's feeling with any of the above comments - its a major fault of mine: I respond to jabs by poking back harder. -- Oded ::.. Kevin: "What about love?" Milton: "Overrated. Biochemically no different from eating large quantities of chocolate." -- from "The Devil's Advocate" ------------------------------------------------------- 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
