Re: RFC: checkflist extra prefixes and post-build hooks

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Wed, 9 Apr 2025 14:06:06 +0200
    From:        Christoph Badura <bad%bsd.de@localhost>
    Message-ID:  <20250409120605.GR27542%irregular-apocalypse.k.bsd.de@localhost>

  | The first one adds a way to tell checkflist to ignore extra or missing
  | files in the destdir through the mk.conf variable

Missing files is a bug somewhere, that should never be ignored, but
fixed instead.   Extra files happens whenever DISTDIR is an existing
system (previously built) and includes all the stuff that needs to be
added to go from a straight build to something workable (including all
of /dev/* of course).   Ignoring those in such a build is entirely
reasonable, but build.sh already has -e to do that, I don't think
extra mechanism is needed for it.

My script that runs build.sh just tests to see if ${DISTDIR}/dev/console
exists (before the build), if it does, it just turns on the -e option
when build.sh is run - since I have done that I have no further problems
in this area, and it is all automated, if I do a fully clean build,
checkflist gets run as intended, if I am updating my test root filesystem
then the extra files that it contains (many) simply get ignored (still
listed in the build.sh log).

  | The second one runs the executables listed in the POST_BUILD_HOOKS mk.conf
  | variable after the do-build and do-obsolete targets.

Why can't that just be done in a script that you run which runs build.sh ?

After build.sh finishes, run whatever else you need - my script does that as
well (for a different reason, but that's irrelevant).   I think here that
everyone has slightly different needs.

kre