I definitely like the idea of having things like this in the tree, and IMO it makes sense to put them in the specific directory so that they can be found, even if that is a bit "ugly."

That said there has been some talk about running things like make makeman via a CI job to detect missed regen/updates, and that would argue for a more canonical location. Adding some folks who I think might have an interest.

About the location, maybe linuxkpi/tools would be better? Like tools related to the Linuxkpi. There probably will be more of them as time goes by!

In D38270#899043, @emaste wrote:

I definitely like the idea of having things like this in the tree, and IMO it makes sense to put them in the specific directory so that they can be found, even if that is a bit "ugly."

That said there has been some talk about running things like make makeman via a CI job to detect missed regen/updates, and that would argue for a more canonical location. Adding some folks who I think might have an interest.

I'd favor a more centralized location for sanity tests. Having a CI job that runs all of them would be great.

That suggests, though, that this test might not be quite right for that since it's more of a 'fix it' script since it does the git rm than a testing script...

The script itself is fine if it's a fixit script (and where it is would be fine, but I'm kinda agnostic). If we wanted to use it as a 'test it' script, though, it would need some work...

Can always make the action an optflag so by default it only spits out if there are "duplicates" or is silent.

We tend to put tools in tools/foo rather than in the sys/ tree directly FWIW.