On 11/05/04, at 12:09 -0400, Michael Jennings <[EMAIL PROTECTED]> wrote:
> > Yes, but you didn't *ask*, you told. Had you asked, I probably > would've worded it differently. :-) I now know what was wrong. In line 5 of the etox configure.in, it's written AM_CONFIG_HEADER(config.h) but if I change it to AC_CONFIG_HEADERS(config.h), it compiles nicely. Apparently the new automake versions do not like AM_..._HEADER but prefers AC_..._HEADERS. I got this info from these automake mailing lists. Now let me rephrase correctly :-p, are you guys going to change this line or must I instruct my scripts to change the line on my machine and compile? > I would say "privilege" rather than "right." CVS is, first and > foremost, a developer tool. Always has been. What's in CVS at any > particular moment may or may not compile, and those who lack insight > into the how's and why's of each module's status are generally > encouraged to refrain from complaints (although patches are always > welcome) because it takes developer time away from more worthy tasks. Ok "privilege" is the right word. I know it's a developer tool. But many people including me want to try out the libraries and install the cool E17 apps. I do not know the "how's and why's of each module's status" but I still wanna help out and understand: in order to make rpms and make life easier for other people with the same type of distro. Because what you guys are doing is terrific and I want more people to share the same pleasure I have in using E. That is why (despite the fact that it's pleasurable and I'm contributing something) I decided to embark on an E17 apt repository project. So far it's advancing. I had to revise all the specs file which seem to be outdated in syntax and style, plus write some cool scripts which extracts info on the modules and buile the rpms. If we wait for really stable EFLs and apps, then we'll be waiting forever and that is not fun! :-p Lay persons wanna have the fun too. Please bear some complaints for E! > You really should check out mezzanine (www.kainx.org/mezzanine/). > After running "make dist" a simple "mzbuild" will create RPM's and > SRPM's for you. You can also build inside a chroot jail > (-r /path/to/jail) or as another user (-u userid) with minimal > difficulty. This also makes building for multiple targets as easy as > using multiple buildroots, which in turn is as easy as invoking > mzbuild multiple times with each chroot path (e.g., "mzbuild -r > /path/to/fc1/root ; mzbuild -r /path/to/fc2/root"). Very cool set of scripts. My building script ressembles yours. Not as elegant of course but which still works and do the job correctly. There are some neat ideas inside yor scripts worth having a look. Thanks a lot. > > ecore-1.0.0_pre7-0.fc1.20040511.i386.rpm > ^^^^^^^^^^^^^^ > I'd recommend 0.YYYYMMDD.fcN myself. Otherwise you're giving > preference to a dist upgrade over a package upgrade. > Yeps. noted. Thanks. With kind regards, Didier. --- PhD student. Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: didierbe at sps dot nus dot edu dot sg Web: http://ssls.nus.edu.sg ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
