Re: FreeBSD ports community is broken

On 18/02/24 12:41, Vasily Postnicov wrote:
> My 50 cents about poudriere: it's definitely not a machine-killer. Just 
> remember to disable tmpfs for too heavy ports (my list includes rust, 
> 0ad, webengine), start with only two jobs (one job is bad because the 
> build can be blocked by fetching or packaging) and set ALLOW_MAKE_JOBS=yes.
> 
> This configuration works fine and without swap consumption on my 32GB 
> computer.
> 
> Another improvement: set MAKE_JOBS_NUMBER to a half of available cores. 
> This way (two jobs each using n/2 cores) you can map your build 
> processes to all available cores.

Some other random suggestions for poudriere:

Using CCACHE helps a lot too. Disk space is not as expensive as it used 
to be. If building for a single OS version and single architecture 8 GiB 
cache can be quite enough.

Poudriere "recently" gained ability to use binary packages for 
dependencies, with safeguards for different options and other things ( 
-b option, in poudriere-bulk(8)). I never used this one, but it could 
help a lot with build times. (this one has been strongly asked for for a 
long time, and it looks like very few users are aware it is now available)


the -S option, is something I would not suggest. At least not unless one 
is able to really understand what is going on; it also has the problem 
that once you end up with a broken repo set the only fix is to start 
from scratch (AFAIK).

-- 
Guido Falsi <mad@madpilot.net>