Re: [E-devel] Nightly build log for E17

[Eugen M. <mi...@gm...>]

Hi list,
I'm sorry if this is actually a repost of a message I wrote a couple of
days ago. However, it may be that my MDA (which wasn't properly
configured back then) failed to send that message. If it is a repost, I
deeply apologize.

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.

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
> 
> Ubuntu 6.10 \n \l
> 
> Linux cluster 2.6.17-11-generic #2 SMP Fri May 18 23:39:08 UTC 2007
> i686 GNU/Linux
> 
> 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
> 
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.

> Failed Packages (and command that failed):
> eflpp make -j 2
> elapse make -j 2
> epdf ./autogen.sh --prefix=/opt/e17
> --cache-file=/tmp/easy_e17/easy_e17.cache e_phys ./bootstrap
> etk_extra ./autogen.sh --prefix=/opt/e17
> --cache-file=/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.

example: 
Failed Packages: eflpp elapse epdf e_phys etk_extra etk-perl Evas_Perl

3. Each project that failed to get built should have a link to its log
something like:

Details about failed packages:
eflpp:
failed command: make -j 2
build log: http://onefang.humbug.org.au/E-build-logs/eflpp.log
...
> 
> Packages with no supported build system:
> eflame, enthrall, esmart_rsvg, euphoria, exorcist, nexus, ruby-efl,
> 
> Skipped Packages:
> camE, embrace, enotes, enscribe, epbb, eplay, erss, etk_server, etox,
> evoak, gfx_routines, lvs-gui, med, notgame, webcam,
> 
> 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.

> 
> Build logs are available at http://onefang.humbug.org.au/E-build-logs/
> 
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)
> 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.
> 
> The web directory does not contain anything that needs to be built.
> 
> The e17/test directory is just a dumping ground for old testing stuff
> that is not meant to be built automatically.
> 
> The e17/docs directory contains documentation.  Some of it can be
> "built" but I have not bothered yet.
> 
> 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.
> 
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:

The nightly build system tries to build everything in the Enlightenment
 CVS or give a reason why it isn't being built. 
For more information about this system, please go to this link: ...
> The "skipped" result means that the nightly build system was configured
> to skip that particular project for some reason.  Those reasons should
> be listed here -
> 
> etox            - Obsolete.
> evoak           - Obsolete.
> enscribe        - Unmaintained, broken, and too old to fix.
> med             - Unmaintained, broken, and too old to fix.
> camE            - Unmaintained, broken, and too old to fix.
> embrace         - Unmaintained, broken, and too old to fix.
> epbb            - Unmaintained, broken, and too old to fix.
> eplay           - Unmaintained, broken, and too old to fix.
> erss            - Unmaintained, broken, and too old to fix.
> lvs-gui         - Unmaintained, broken, and too old to fix.
> notgame         - Unmaintained, broken, and too old to fix.
> webcam          - Unmaintained, broken, and too old to fix.
> enotes          - Unmaintained, broken, and too old to fix.
> etk_server      - Uses huge amounts of RAM, so may fail.
> gfx_routines    - This was just a bunch of graphics tests.
> 
> 
> NOTE: sometimes an ERROR is the result of a failed dependency.  The epdf
> project is a prime example, as it often requires the very latest poppler
> version, and not everybody is using the latest version of everything.
> Some people are quite happy running a slightly older, stable OS.

Of course, these are all my opinion, and you know what those are like
... :)

-- 
Eugen Minciu.

Wasting valuable time since 1985.