On Tue, 17 Jul 2007 01:45:00 +1000 David Seikel <[EMAIL PROTECTED]> babbled:
> On Mon, 16 Jul 2007 10:28:07 -0500 "Nathan Ingersoll" > <[EMAIL PROTECTED]> wrote: > > > On 7/16/07, David Seikel <[EMAIL PROTECTED]> wrote: > > > > > > > So you are you complaining about API changes breaking the CVS > > > > build and not getting fixed, > > > > > > Yes. > > > > This is actually a series of problems, not just one person taking the > > time to fix CVS, though that is part of it. It also indicates we are > > lacking good review of changes, user feedback is not reaching the > > developers that will fix it, and maintainers are not updating their > > module as dependency changes occur. > > > > An automated nightly build could improve the build break detection. > > I do a mostly regular build of almost everything, which is why I notice > these things. I'll be happy to setup regular automated builds. > > Where would an automated nightly build best be run? Where would the > results be delivered? Since we are scattered all over the planet, > whose night should be used to define "nightly"? we have servers! e1.enlightenment.org and e2.enlightenment.org. we can install any locally required packages for builds and have them automated. build + install (into a specific prefix - eg /opt/e17). only a matter of scripting it up so it is automated and won't fail if not done as root (we need to do it as a user here for security reasons considering what a build can actually do). currently the builds should not fail if done as a user. > Many other questions need to be answered to set this up. > > Off the top of my head. sf.net has a compile farm that can be used for > such things and I already use it for another project. Then we can do > builds on several platforms. I have seen other projects get the > results of the nightly build sent as a single email to their dev > mailing list each night. aaah - other platforms - that is a problem. we can do a nightly build for at least x86 (and x86_64). that should be sufficient for us for now. other arches are good - but we only have so much in the way of resources. we could do ARM builds via scratchbox the same way we do x86/x86_64 easily. i assume ppc could be done in a similar way if someone wants to set up a scratchbox ppc env. > I live an the same side of the planet as raster, so I share his night, > but I work at strange hours so that I can deal with my USA client in > real time (and not disrupt my local clients servers during local > business hours), so I don't really care what time it runs at. Probably > doesn't matter so much what time, so I'll suggest a completely > arbitrary GMT midnight to start the builds. Probably take one to two > hours to complete each build, but on the sf.net compile farm, they can > all build at the same time. On the other hand, trying to dodge compile > farm busy times might be worth while. as i said - "we have the power" :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------------------------- 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
