Re: Default NO_CLEAN=yes in 15+

Shawn Webb <[email protected]> Tue, 23 Jul 2024 20:08:17 +0000
Newsgroups	gmane.os.freebsd.architechture
Message-ID	<ia2xwmohoomnica7vp7hotd7sknovyyb3hgkfrx6blekbx6qdn@aax3blyqxcer>
On Tue, Jul 23, 2024 at 03:58:13PM -0400, John Baldwin wrote:
> The buildworld and buildkernel targets include a "clean" step before building
> objects dating back before my time to 'make world' (I haven't looked to see
> how far back it goes).  To permit incremental builds, this step can be skipped
> via NO_CLEAN=yes.  This step is a bit unusual in build systems however.  Most
> build systems have separate commands for building vs cleaning (e.g. 'make all'
> vs 'make clean') and over time FreeBSD's build system has gained dedicated
> clean targets as well (cleanworld and cleankernel).  For myself, I always
> use NO_CLEAN=yes when building worlds and kernels.  If I need a clean build
> I use the dedicated clean targets (e.g. cleanworld) first.  In particular,
> cleanworld/cleankernel are far more efficient since they use a single
> recursive 'rm' whereas the "clean" step involves a full tree walk with
> nested make invocations of the 'cleandir' target.
> 
> A few years ago, Ed Maste added a MK_CLEAN option to src.opts.mk to as a
> WITH/WITHOUT knob for the "clean" step similar to NO_CLEAN=yes.  To preserve
> existing behavior this knob currently defaults to on, but I know Ed's goal
> was to eventually flip the default so that NO_CLEAN builds would be the
> default.  I would like us to do that starting in 15.

It would make sense to me to default MK_CLEAN=no in release branches.
Perhaps stable branches, too. While I don't hold a strong opinion on
the matter, I would prefer MK_CLEAN=yes to remain the default on the
main branch.

I can't give tangible examples, but I remember running into weird
issues occasionally when using `make buildworld WITHOUT_CLEAN=yes` in
main. I probably should do a better job at documenting those
(infrequent) issues when they arise.

> 
> Further off, I would suggest that we remove the "clean" step outright,
> perhaps in 16.x.  Regardless, we will need to update documentation to
> prefer the clean targets over WITH_CLEAN=yes if our docs do not do this
> already.

I would not be in favor of removing the clean step. Removing clean
outright seems like a step too far--a potential POLA violation, even.
Please keep clean in.

Thanks,

-- 
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc
signature.asc (application/pgp-signature, 833 B)