We just found a fun thing in devel/libgdata with Antoine. Specifically, the port started building, and then crashed halfway through.
What happens is that the port does not list gtk+2 in its build dependency tree. So, at the start of the build, gtk+2 was installed (coincidence, due to some other stuff building) then, during the middle of the build, the port that required gtk+2 got finished, *and gtk+2 got deinstalled*... boom. That's perfectly alright from dpb's point of view: it maintains a list of packages it needs. So, if you don't record optional dependencies, or disable them, sometimes the configure script will pick them up, and they will vanish later. That's exactly the kind of stress test dpb -J is supposed to provide. Only, it might be a bit funny to figure out the exact sequence of events, since packages installed just got less static...
