From: David S. <on...@gm...> - 2007-07-24 22:15:08
|
Sorry about not getting back to this sooner, I've been dreadfully ill. On Sat, 21 Jul 2007 15:36:26 +0300 Eugen Minciu <mi...@gm...> wrote: > I have a couple of comments about the format of this build log. > Obviously, this is a bikeshed thing and I'll avoid posting about it > again. Obviously, these comments are just my impressions and you > needn't share them. >=20 > Excerpts from David Seikel's message of Sat Jul 21 06:13:57 +0300 > 2007: > > Build log for Enlightenment DR 0.17 on 2007-07-21 13:11:41 +1000 > >=20 > > Ubuntu 6.10 \n \l > >=20 > > Linux cluster 2.6.17-11-generic #2 SMP Fri May 18 23:39:08 UTC 2007 > > i686 GNU/Linux > >=20 > > autoconf (GNU Autoconf) 2.60 > > automake (GNU automake) 1.9.6 > > ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 > > 2005/12/18 22:14:06) > > gettext (GNU gettext-runtime) 0.15 > >=20 > 1. The list of projects that fail should probably be the first thing > to see after the name of the OS. The detailed list of autotools > versions and such should probably only be detailed in the log on the > web page, or near the end of this message. Slowly but surely I'm beating the report format into some sort of useful shape. Something like this is planned. > > Failed Packages (and command that failed): > > eflpp make -j 2 > > elapse make -j 2 > > epdf ./autogen.sh --prefix=3D/opt/e17 > > --cache-file=3D/tmp/easy_e17/easy_e17.cache e_phys ./bootstrap > > etk_extra ./autogen.sh --prefix=3D/opt/e17 > > --cache-file=3D/tmp/easy_e17/easy_e17.cache etk-perl make install > > Evas_Perl make -j 2 > 2. The list of failed projects should (at least in the beginning of > the message) be a single line (possibly wrapped) of text. >=20 > example:=20 > Failed Packages: eflpp elapse epdf e_phys etk_extra etk-perl Evas_Perl Another good idea I'll consider. > 3. Each project that failed to get built should have a link to its log > something like: >=20 > Details about failed packages: > eflpp: > failed command: make -j 2 > build log: http://onefang.humbug.org.au/E-build-logs/eflpp.log Already planning on including a link to the log file. > > Successful Packages: > > alarm, bling, cpu, deskshow, eclair, ecore, edb, e_dbus, > > edje_editor, edje, edje_viewer, edvi, eet, efreet, elation, elicit, > > elitaire, e, embryo, emotion, emphasis, empower, emu, engage, > > engrave, engycad, enhance, enity, enterminus, entice, > > entrance_edit_gui, entrance, entropy, envision, epeg, ephoto, > > epsilon, equate, esmart, estickies, etk, e_utils, evas, evfs, > > evolve, ewl, examine, exhibit, exml, expedite, express, extrackt, > > feh, flame, forecasts, iconbar, imlib2_loaders, imlib2, > > Imlib2_Perl, imlib2_tools, language, mail, mem, mixer, moon, net, > > news, pesh, photo, rage, rain, screenshot, scrot, slideshow, snow, > > taskbar, tclock, uptime, weather, winselector, wlan, > 4. The list of projects that were successfully built shouldn't be > written, I think. The whole point of this system is to tell people > what projects haven't been built. A lot of lines of text are taken up > by the projects that haven been successfully built. It's a sanity check. Did package X not get built because it failed, was skipped, or it's not even in the list of packages to test? This list of successful packages covers that last one. If a new package gets added, and doesn't show up on any of those lists, the author of the new package knows that the list to be checked needs updating. I'll be keeping the list up to date, but other devs should be able to tweak the list as needed. Especially if I'm ill and can't get anything done. B-) > > Build logs are available at > > http://onefang.humbug.org.au/E-build-logs/ > >=20 > 5. The build logs should be dated, but I'm sure that will happen > (something like: http://onefang.humbug.org.au/E-build-logs/2007/07/21) Don't think we really want to keep old logs, or if we do, not too many old logs. > > The nightly build system tries to build everything in the > > Enlightenment CVS or give a reason why. Currently eterm, e16, > > e17/docs, e17/test, and web are not built. Feel free to enlighten > > me about any decisions. > >=20 > > The web directory does not contain anything that needs to be built. > >=20 > > The e17/test directory is just a dumping ground for old testing > > stuff that is not meant to be built automatically. > >=20 > > The e17/docs directory contains documentation. Some of it can be > > "built" but I have not bothered yet. > >=20 > > The eterm and e16 directories are not currently being built because > > the build script used as the basis for the nightly build system > > didn't support those. This may change. > >=20 > Maybe I'm not understanding this and this part isn't really a part of > the log. But if it is, I think this is maybe a bit too verbose. How > about something like: >=20 > The nightly build system tries to build everything in the > Enlightenment CVS or give a reason why it isn't being built.=20 > For more information about this system, please go to this link: ... Already done. Just waiting to be healthy enough to get back to it and actually create the files on the e2 web server. |