strange port build problems

[Frank Wall]

You (Joe Marcus Clarke) wrote on Sat, Jul 26, 2008 at 07:16:24PM CEST:
> If you're not using the Tinderbox port, there was a bug with OPTIONS
> that was only recently fixed.  Adding WITHOUT_LIBSSH2 to one of the .env
> files was a known workaround.  I highly recommend you either go with the
> port, or move to the 3.0 snap from CVS.

Thank you for your reply. I was using the FreeBSD port that should
not contain this bug. Well, I still did not found out what the problem was.
I have deleted the curl package, recompiled, and everything is fine now.

Currently I got about 360 ports in my tinderbox and they all compile
without any problems. Nice :-)

> Note: ports will only be rebuilt if they have changed.  Therefore, if
> you've built everything in the database yesterday, and none of the ports
> have had a PORTREVISION bump, then there's nothing for TB to do.  You'd
> have to run tinderbuild with the -cleanpackages argument to override
> this.

The README confused me, because I got a wrong understanding of this
tinderbuild option:

 -norebuild      : do not force a rebuild of packages specified on the
                   command line

I read "do not force a rebuild" and my conclusion still is "if I do not 
set -norebuild, tinderbox will always force a rebuild of the package". 
Maybe I have to grab an english dictionary and teach myself further ;-)


Kind regards


Frank