Fw: cvs commit: ports/ports-mgmt/tinderbox Makefile distinfo pkg-plist ports/ports-mgmt/tinderbox/files patch-buildscript patch-www-exp__core__TinderboxDS.php patch-www-exp__module__moduleBuildPorts.php pkg-message.in
Joe Marcus Clarke
marcus at freebsd.org
Thu Jun 5 15:01:25 EDT 2008
Ion-Mihai Tetcu wrote:
> May I suggest incorporating this patches?
I've already put some in HEAD with miwi showed them to me. I don't like
arbitrarily printing the NO* macros, so I'll look at doing a whole env dump.
>
> (the number of displayed ports should be configurable but that's
> something to do for 3.0 if the templates/clases change)
>
>> Begin forwarded message:
>>
>> Date: Tue, 3 Jun 2008 13:24:58 +0000 (UTC)
>> From: Ion-Mihai Tetcu <itetcu at FreeBSD.org>
>> To: ports-committers at FreeBSD.org, cvs-ports at FreeBSD.org, cvs-all at FreeBSD.org
>> Subject: cvs commit: ports/ports-mgmt/tinderbox Makefile distinfo pkg-plist ports/ports-mgmt/tinderbox/files patch-buildscript patch-www-exp__core__TinderboxDS.php patch-www-exp__module__moduleBuildPorts.php pkg-message.in
>>
>>
>> Added files:
>> ports-mgmt/tinderbox/files patch-buildscript
>> patch-www-exp__core__TinderboxDS.php
>> patch-www-exp__module__moduleBuildPorts.php
>> Log:
>>
>>
>> Plus 3 local (port) patches:
>> * in "Current and Latest Builds" (?action=latest_buildports) increase the number
>> of ports displayed from 20 to 30
>
> (the number of displayed ports should be configurable but that's
> something to do for 3.0 if the templates/clases change)
My web-fu sucks. I can do it, but it never turns out looking good. I
will defer to one of our experts to get configurable displays.
>
>> * in ports built for a build view (?action=list_buildports&build=something)
>> when sorting is done by Last Build Attempt sort descending (latest build first).
>
> Here maybe we need per category pages.
See above.
>
>> * in build logs, add: [1]
>> - building for: (ie: "6.3-STABLE amd64")
>> - Makefile ident: (ie: "$FreeBSD: ports/ports-mgmt/tinderbox/Makefile,v 1.41 2008/05/19 20:00:16 itetcu Exp $")
>> - prefixes: (ie: "LOCALBASE=usr/local X11BASE=usr/local")
>> - NO* env vars: (ie: "NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes")
>
> A more complete solution would be to have all exported vars from *.env
> displayed. Maybe other settings as well (like ccache) or maybe they
> should be displayed in the "info area"-box for the build / ports tree.
Yeah, I'm looking into this. It shouldn't be too hard to do in HEAD.
Joe
--
Joe Marcus Clarke
FreeBSD GNOME Team :: gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome
More information about the tinderbox-list
mailing list