can someone test this two issues I have with tinderbox current

[olli hauer]

Hi,

maybe I'm wrong but have two issues with tinderbox current.

1) "./tc tinderbuild ..." works only if I added the port before with
"./tc addPort ..."

According the documentation from 3.3+ this should be no longer required
http://tinderbox.marcuscom.com/README/c228.html


./tc tinderbuild -nullfs -b 7.3-FreeBSD devel/apr1
ERROR: Port, devel/apr1 is not a valid port for build, 7.3-FreeBSD
tinderbuild: creating makefile...
tinderbuild: Creating build directory for 7.3-FreeBSD
7.3-FreeBSD: cleaning out /mirror/tinderbox/7.3-FreeBSD
makeBuild: extracting jail tarball
....

./tc addPort -b 7.3-FreeBSD devel/apr1

./tc tinderbuild -nullfs -b 7.3-FreeBSD devel/apr1
tinderbuild: creating makefile...
tinderbuild: Creating build directory for 7.3-FreeBSD
7.3-FreeBSD: cleaning out /mirror/tinderbox/7.3-FreeBSD
*** FAILED (rm /mirror/tinderbox/7.3-FreeBSD)
makeBuild: extracting jail tarball
...
Build goes on ...


2) It seems with 3.3+ dependencies are no longer calculated correct.

Test case:
- copy via hook_postBuildExtract a custom /etc/make.conf with the following
  line "WITH_BDB_VER=47" into the build.
- chroot into the build
- change to devel/apr1
- make -V USE_BDB => 47

If the build starts db42 is added to the mix and starts later additional
the db47 build so the build fails.

Cross check:
./tc getDependenciesForPort -b 7.3-FreeBSD -d devel/apr1 -t LIB_DEPENDS
textproc/expat2
databases/gdbm
converters/libiconv
databases/db42

The only workaround is to use the env/build.$build file which is not
always the best solution since conditions cannot be defined.

echo WITH_BDB_VER=47 >> env/build.7.3-FreeBSD

Now the correct db version is choosen during build time.
I remember I had no times trouble with tinderbox 2.4/3.2 and a
custom make.conf.

If I find some spare time I will try the same with an fresh
system and tinderbox 2.4/3.2 to verify this behavior.