I had submitted a patch in bug 162397 to add this target to bsd.port.mk, and worked quiet well while using tinderbox. It is possible that the target may need to change if the variables in it are not found in pourdiere: .if !target(add-plist-buildinfo) add-plist-buildinfo: .if defined(PACKAGE_BUILDING) @${ECHO_CMD} "@comment Build details: ${BUILDHOST}|${JAIL}|${BUILD}|${PORTSTREE}|${BUILDDATE}" >> ${TMPPLIST} .endif .endif This information can be tuned to supply more information, or less, depending how we feel it would best suit our/customer needs. From an IRC chat: it is quite possible a build server could produce bad packages, and possible that on Monday 10.1-amd64 is built on beefy1 while on Wednesday it is build on beefy8 and produce a broken package. Unlikely, but possible.
The problem here is that add-plist-buildinfo was removed for staged ports. It needs to be rewritten to use PKG_NOTES instead.
I feel the best way for tinderbox to do this would be to set USE_LOCAL_MK in the environment/make.conf and replace Mk/bsd.local.mk with one containing whatever targets/variables tinderbox needs.
Bapt brought up an excellent point on IRC. Anything we do here needs to generate packages that are reproducible.