Re: Build failure tooling improvements

[Rob Whitlock <rwhitlock22%gmail.com@localhost>]

> On Mar 20, 2025, at 3:35 PM, Benny Siegert <bsiegert%gmail.com@localhost> wrote:
> Am 20.03.25 um 18:29 schrieb Jonathan Perkin:
>> So, how about a different approach.  What would you like me to work on? What features would you like to see, and would actively use?  What is your ideal workflow?  What would it take for your workflow to include cross-platform checks prior to commit?  What resources do you need to help ensure each individual commit is as high-quality as possible?
> 
> Maybe a post-commit hook to build the package and its direct dependencies after a commit?
> 
> In the src tree, there is a list where post-commit build failures are posted by a script, and that way they are usually fixed quickly.

Many of the errors I run into are a result of me using non-default options, particularly the doc option. Having a commit hook as described above that tests packages with the doc option I believe would catch those errors early. I'm guessing that many of the PLIST errors are because an update to doxygen makes the built files of dependencies of doxygen generate different files, so if you were looking to limit the number of packages built with the doc option, it might be 95% effective to only build the packages that rely on doxygen.

> -- 
> Benny