Tinderbox newbie questions.

[Dan Casey]

Hopefully someone here can answer a few questions I that I could not get
answered in the readme.

The reason I am building my own packages, is because I need different
compile time options from what FreeBSD chose to compile with. For
example I don't think I should have to install xorg just because I want
to use vim as an editor. 

I would like to use only packages on my production servers.  Tinderbox
seemed like a good solution.  I am running into a few problems though.

1. The documentation is very limited. It's free, I know. Not a
complaint, just a statement :)

2. For each port that I make I have to select the appropriate options
and keep the /var/db/ports/package/options file.  When using tinderbox I
do not even get the ncurses menu.  While this is definitely a good thing
for automation, I have to manually cd to every port (and it's
dependencies) and run make options.  Please tell me there is some way to
handle this that I don't know about.
Just a thought, but when you run ./tc addPort  I think it should have to
pick all your options (recursively).

3. Is there a way to automatically queue a port build based on rule like:
     a. A port (or build-dep of that port) has a vulnerability.
    b.  If something in freebsd was updated (like ssl) all packages
built off of that now have to be recompiled.


4. Is it possible to package a kernel and base system?  So for I have
every box building there own.  I have stripped out a lot from the SMP
kernel, and also I need to make modifications to syslimits.h before
compiling. 



Thank you much.