Re: Combining NOT_FOR_* and BROKEN_ON_*

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Thu, Apr 03, 2025 at 10:29:52AM +0100, Jonathan Perkin wrote:
> My opinion is that BROKEN* is a solution looking for a problem, and I've yet
> to hear a reason why having it makes pkgsrc better.

When I look at bulk build reports, I don't want to see the same error
again and again - it can be analyzed once, marked with BROKEN*
explaining the problem, and will not show up as a build failure in the
next bulk build, saving me from having to remember it, and other
people from analyzing the same problem again. It also saves time in
the bulk build (installing the dependencies, configuring, building
until it fails).

If someone is interested in a package, they try building it, see it's
BROKEN and can either decide that they don't spend the time to fix it,
or remove the BROKEN line and work on it.
 Thomas