Ticket #14796 (pike): please commit

[Anders F Björklund]

Jordan K. Hubbard wrote:

> Either way, you've provided a nice abstraction boundary for the  
> developer and can refine the definition of "chroot" as various edge  
> cases are found without having to disseminate updated instructions  
> to everyone.  I probably updated my chroot definition about 20  
> times while I was creating that buildall.sh script I just mentioned  
> and I still don't think I got it totally right in terms of "minimum  
> functional footprint."

chroot was discussed last year, but somewhat discarded as overkill  
compared to trace mode and flexible logging... I updated the chroot  
scripts from OpenDarwin to install Tiger instead, but there never was  
a "minimum footprint" decided so it installed most of it - or about 4  
GB in total. (this was when installed from the Mac OS X + Xcode Tools  
installation packages, before any pruning)

I do think a chroot setup, combined with the SDKs and cross- 
compilation, could allow for building a lot of binary packages.

--anders