@forrie: "I've been asked to take a few select ports from /usr/ports and create a 
build environment.
This presents a few technical issues, some of which can be dealt with by 
overriding certain variables like PORTSDIR, NOPORTDOCS, et al.
The second problem is ports are updated with some frequency, and we need 
to keep a stateful build environment so that each dependency is there 
"as-is" during that build.
I figure I could lessen the pain of hacking variables by simply 
snapshotting the /usr/ports struture, placing that into a separate 
directory and then modifying PORTSDIR and DISTDIR in the build process.
So before I go too far here, I wonder if someone else has done this - 
perhaps some examples/tips/feedback would be appreciated.
Thanks....."
    @forrie: "Hi there,
We're taking the angle of a top-level makefile right now - to call the 
individual builds to the ports we require, then an install, then a "make 
package" (possibly via direct pkg_create).
This is for a project that requires some control over versioning - I 
wanted to exploit the development environment provided by the ports 
structure, and not have to reinvent the wheel, necessarily....
Thanks!
<quote>"
{'source': 'USENET', 'other_information': '{"reply_count": 1, "forum_name": "lucky.freebsd.ports.20140828.mbox"}', 'file': 'data/output/usenet-lucky.freebsd.parquet'}