[clc-devel] clcbuild: first test
Hi everybody, I finished the first automated compilation of all clc/contrib ports on a machine with only /base ports installed. Quick summary for the impatient: 306 Successful, 240 Failed. Full details at http://www.varlock.com/blosxom.cgi/cruxprojects/clcbuild/index.html As I expected, I found quite a number of ports that could not be compiled properly, since many times maintainers (me included: see xpdf, fox: failed) tend to skip listing of /opt dependencies, ie: - xfsprgs depends on gettext - lesstif depends on xfree86 - wmclock depends on windowmaker - tetex depends on xfree86 - blender depends on python - fvwm depends on xfree86 some of them are mandatory (xfsprogs), some are only a question of footprint mismatch (tetex). Another note: Pango could not compile, consequently gtk2 failed, and so many ports depending on gtk2: gnome, etc. Something similar happened to kde ports (lesstif failed), at least we're impartial regarding DEs :-) Apart from ports failing for my particular setup (ie: alsa-driver), can/shall we fix the failing ports? It could require some time, but I think It's very important to have a well-tested and consistent contrib collection; besides after some initial work now, things are likely to go much better for the future. Plus we can take our time, since we don't have deadlines of any sort. Idea: For the moment we could use a separate dependency file thanks to latest addition to prt-get by Johannes (see "opt dependencies" thread), just not to play too much with the cvs repo. NB: I'm not trying to force anybody into fixing these issues, as soon as I get some spare time I'd like to have a deeper look at every single log myself, but any help /comment is really appreciated :-) Best regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com
If something depends on opt/xfree86, for example, I usually put 'xfree86' as a dependency and assume that the other things like fontconfig and freetype2 are already installed. Is this the right thing to do, or should I be adding all the packages to the dependencies line? * Simone Rota <sip@varlock.com> [03/08/04 12:59]: [snip]
NB: I'm not trying to force anybody into fixing these issues, as soon as I get some spare time I'd like to have a deeper look at every single log myself, but any help /comment is really appreciated :-)
Wow, 44% of the ports in contrib failed. That doesn't look very good. Perhaps there could be a third category of 'UNTESTED' (or something) for the ports that didn't even start to get built because previous dependencies failed. -- Robert McMeekin <rrm3@rrm3.org>
On 03/08/04 23:31 Robert McMeekin wrote: Hi Robert,
If something depends on opt/xfree86, for example, I usually put 'xfree86' as a dependency and assume that the other things like fontconfig and freetype2 are already installed. Is this the right thing to do, or should I be adding all the packages to the dependencies line?
Yes, I think this is what the clc guidelines say. Btw, I just noticed the guidelines also express the possibility of avoiding listing opt ports (together with base); if I remember well we more or less decided to have /opt listed in dependencies so a little correction is needed.
Wow, 44% of the ports in contrib failed. That doesn't look very good. Perhaps there could be a third category of 'UNTESTED' (or something) for the ports that didn't even start to get built because previous dependencies failed.
I think many of them would successfully build on a 'more standard' system (with all or the most common ports from opt installed), so the situation might not be so bad as it appears from statistics. Regarding 'UNTESTED', I think it is a good idea, I'll see if I can add the distinction you suggested in next versions of the test script. regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com
On Mon, Mar 08, 2004 at 05:31:13PM -0500, Robert McMeekin wrote:
If something depends on opt/xfree86, for example, I usually put 'xfree86' as a dependency and assume that the other things like fontconfig and freetype2 are already installed. Is this the right thing to do, or should I be adding all the packages to the dependencies line?
I would suggest no. The new "external dependency list" feature of prt-get seems to be a much smarter solution than to put 'gettext pkgconfig freetype2 expat glib2 libpng fontconfig atk xfree86 pango gtk2' in any gtk2 depended port ;)
* Simone Rota <sip@varlock.com> [03/08/04 12:59]: [snip]
NB: I'm not trying to force anybody into fixing these issues, as soon as I get some spare time I'd like to have a deeper look at every single log myself, but any help /comment is really appreciated :-)
Wow, 44% of the ports in contrib failed. That doesn't look very good. Perhaps there could be a third category of 'UNTESTED' (or something) for the ports that didn't even start to get built because previous dependencies failed.
I had a quick look at my failed ports and, luckily, found only a few real errors. Most failures are caused by the following issues: - all gtk dependent ports failed, because the configure script could not find the installed gtk libs. I guess a 'ldconfig' could solve this - MTA replacements will generally fail, because /usr/bin/sendmail is already installed - ports which requires an specialized user/group like bind, squid - apache and all depending, because a call of 'hostname -f' within the Pkgfile produces an error ? Thanks to Simone for running this test Jürgen -- juergen.daubert@t-online.de
participants (3)
-
Juergen.Daubert＠t-online.de -
Robert McMeekin -
Simone Rota