On 07/03/2014 11:52 AM, Gordan Bobic wrote: > Sure, but the time it takes to rm -rf the build root and then untar > a cached build root copy is a non-trivial fraction of the build > time for a lot of the packages. It is certainly not trivial when > you multiply it by around 2,000 for the number of packages you are > going to need to build. that solves one problem but creates lots others - eg. the builds resulting from this run wont be usable since they will have wierd and indifferent linking if its just a case of creating a knowledge pool about what does and does not otherwise build, to throw away the results, then sure - this would be marginally faster ( the time to build the base mock root is about 21 seconds on th A15 node were using ). But if you intend to use the resulting content, I cant stress enough - use mock. > From experience, anything you can do to get past the first stage > build faster is usually a good idea if hardware is limited - and > on ARM it usually is. Even on something like the Arndale Octa or > the new Chromebook which have 3-4GB of RAM and 8 cores, building which chromebooks are these ? I still think the server grade ARMv7 stuff available these days is much faster and capable. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc