On Wed, 18 Jul 2007 12:30:53 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote:
> On Tue, 17 Jul 2007 10:14:58 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > Attached is the result of a first cut at a nightly build script. > > Early days, baby steps, don't pick over the little details. We can > > start with the basics and work up to more features later. > > > > For now I can run this on my boxen while it gets developed further. > > Move it to the E servers and volunteer boxen when it's more mature. > > > > Currently it only compiles stuff that uses autofoo. Some things are > > skipped, mostly due to being deprecated or broken and unmantained. > > Most of what is skipped is in misc. Everything in e17, misc, and > > e_modules is included except for the e17/test and e17/docs > > directories. > > can you... put the script in cvs somewhere? tough to talk about > something we can't see. I'm modifying easy_e17.sh. morlenxus has his own svn server that includes it. http://omicron.homeip.net/projects/#easy_e17.sh My changes are committed to that svn server, and morlenxus is also pitching in with relevant changes. There is also a small wrapper script that just calls easy_e17.sh then uses sendmail to send the results. Seems to work fine sending to one of my email addresses, but fails when sending to this list. I blame gmail and sf.net not talking to one another properly, I've had issues with that in the past. This morning there would have been two automated summaries sent if it was not for this email problem. One for Ubuntu/x86 and one for YDL/PPC. I'll wait a few days to see if a bounce is sent. When I've had this problem in the past, neither gmail nor sf.net bothered to send bounces. In the end, I might just subscribe one of my other email addresses to the list. Just so we have something to look at, I'll manually send one of the summaries as it would normally appear. > > Do we need more information, less information, actual build logs to > > be stored somewhere, etc? Throw in e16, eterm, e17/test, and > > e17/docs just for completion? > > personally - i think this needs an explicit list of things to build > (and thus the order to build them in). doing it as a user is trivial > - just need to do a --prefix=/path/to/user/owned/dir in configure. > the rest is just a matter of $PKG_CONFIG_PATH, $PATH, > $LD_LIBRARY_PATH then > > cvs update -dP > for I in `cat build-list`; do build.sh; done >& build.log > > and a build.sh (or a shell func) that runs the autogen.sh, make and > make install with a low priority with nice + ionice. easy_E17.sh already does all that and more, which is why I started with it. > the build log doesn't need to be fancy or pretty - just needs to be > all the raw output of the whole build. > > > I think a nightly email to this list would be the most useful, just > > stashing the results away on the web somewhere makes it too easy to > > ignore. > > don't even think we need that much - just stashing the results in a > web page somewhere is enough Stashing it all on a web page means that people will not bother to look at it. Sending a built/not built summary to this list means that people will actually read it. Stashing the full build logs on the web is good, it doesn't fill the list with tons of shit no one needs to look at, and the one or two people that note that their project is not building know where to find the full build log to investigate further. I'm basing this initial version on what I've seen working for other projects with lots of sub projects. > > For the curious, I'm modifying easy_e17.sh to do this, as I'm very > > familiar with it. I've discussed this with morlenxus, and we have > > agreed to add a few things to easy_e17.sh to make it better for this > > type of work. > > > > TODO - > > > > Remove need to be root/use sudo. Done. > > Support things that don't use the autofoo three step. > > Add qemu / scratchbox support for hardware / OSs we don't have test > > boxen for. > > Maybe create .rpm files on RPM based distros and .deb files on > > Debian based distros. > > BTW, while on the subject of automated testing, I've been asked if > > E17 supports accessibility stuff. Apparently he wanted to use a > > particular automated GUI test system that uses that. As far as I > > know, we do not support that. Any thoughts? > > you will need to be more specific with "supports accessibility > stuff". e make no particular efforts one way or another for > "accessibility". if something works or not depends on the details of > what it does. It was a request from a fellow TSS developer, he was not more specific than to mention that he wants to use some automated test tool.
signature.asc
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
