Tinderbox quirks

[Ade Lovett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Nov 25, 2005, at 10:30 , Joe Marcus Clarke wrote:

> [multi-phase tinderbuild]
>
> ccache errors relating to NFS, coredumps, etc.  On my i386 box on  
> which
> I use NFS, phase 2 comes in very handy.

Well, it was a pretty trivial patch, so there's now a new -onceonly  
flag (default off) to tinderbuild which suppresses the second phase,  
for those that want it.

> Hmm, I'd have to look into this.  Both proc file systems are mounted
> into the Build, and should be functional.

Actually, only /compat/linux/proc was mounted.  I've added code to  
HEAD to also handle /proc, but the codebase has diverged so  
significantly between 2.x and HEAD, I'm really wary of committing a  
fix there, for fear of breaking things, particularly as I no longer  
have a 2.x tinderbox around to verify things with.

>>>> - ports and dependencies which are IGNORED don't show up in the
>>>>   current build page, hard to find reasons why builds fail.

Yup.  Took make ages to figure out why a gnome-2.13.x build wasn't  
doing everything, until I picked up on librsvg2 being a dud (still  
is, BTW, even after today's patch by ahze).

I was thinking of adding a 'DUD' entry to the last_status ENUM in  
build_ports, and having the web UI make the status box yellow (or  
some other appropriate color).  As things stand, I don't see a  
particularly easy way to add the actual BROKEN/IGNORE message into  
the mix -- it'd really need to be a new element in the build_ports  
table, rather than overloading, say, last_built_version, and I'm not  
sure whether we want to be dinking with the 2.x schema.

I guess something like this could go into HEAD though.  Thoughts?

- -aDe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDh9YepXS8U0IvffwRAjfUAKCCDeFf95aNlM17FEmHGxhfz3qjcwCgm3/I
N3DdfOj9IInu7i+dGtbMeKs=
=q/R+
-----END PGP SIGNATURE-----