with the recent changes, it seems that mfs is now good enough that you can build ports under it.
I've just tweaked dpb proper to make things slightly easier. to do so: - dpb needs WRKDIR size statistics, which you have to collect with -s. Those will now be entered into a "rolling log", similar to what goes on with build-stats/arch, so that you don't have to figure out where the previous ones live. - you need an mfs filesystem. The location for ports builds is currently hardcoded as /tmp/pobj - if you use -M or mem=... in an hosts file, then dpb will force WRKOBJDIR=/tmp/pobj for selected ports. Specifically, it can keep track of the total size of ports building on a given host, up to the value you give. - in case of breakage, be aware that "make clean" must be made aware of the proper WRKOBJDIR... Following Bob Beck's advice, be careful, and do not be overly optimistic. Specifically, if your mfs + memory usage no longer fits inside main memory, then bad things will happen, performance-wise ! Integrating rusage stats might be interesting, but it will be a bit tricky, as actual memory usage will tend to "spike" and max usage doesn't quite cut it... especially for moz ports which are well-behaved apart from the final link phase...
