Date: Sun, 18 Feb 2024 17:22:27 +0100 From: Guido Falsi <mad@madpilot.net> To: Vasily Postnicov <shamaz.mazum@gmail.com>, Aryeh Friedman <aryehfriedman@gmail.com> Cc: ports@freebsd.org Subject: Re: FreeBSD ports community is broken Message-ID: <651d5fee-6989-4953-bfac-bce87dfcd54a@madpilot.net> In-Reply-To: <CADnZ6BktN7yhr_bOpOrP4GukwF78dttvT7Hgwj2s9gLi0w-nXg@mail.gmail.com> References: <20240218015843.34c5d078@rimwks.local> <7q6ep7m2eee6yqtxftlwkhuwdkssd74vjow55txms7lkokazfu@grrqllhefges> <20240218174921.a8082649142dd43a469bebfa@dec.sakura.ne.jp> <4ekno7iwxvdlw4xeholcrxuuazmcstxkqyidrz27ni43lzu6wg@3ro6r5b2vhoi> <CAGBxaXnBTF=-V55pbQNJ5czRihAOZvAt53UNzzYT=bgBiqwQ0w@mail.gmail.com> <CALH631kcLJ9KFREovOQXmcbTi1Mbj_dCQuhBqLX%2BPbO6gKJj_w@mail.gmail.com> <CAGBxaXm0PsZRaJsPRxBTyAMxMhe%2BOU_cWErenm-upP0k0=thew@mail.gmail.com> <CADnZ6BktN7yhr_bOpOrP4GukwF78dttvT7Hgwj2s9gLi0w-nXg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?651d5fee-6989-4953-bfac-bce87dfcd54a>