[thunkpad]

> I mean, if you start building an auto-fixer pipeline for an auto-linted error... then is that error actually valid in the first place? Probably not.

Yeah that does sound like a waste of time for a relatively small project.

But I actually think this makes perfect sense once you factor in how massive the effective codebase of Debian is. It's also a much different beast; there are benefits and costs to moving more slowly and methodically. Making seemingly small architectural changes (like the switch from 'extra' to 'optional') is awkward just because of the structure of the project.

Anything to take tedium off the plates of devs who are committing upstream in preparation for the next release has to be a good thing, right?