Hello all, sorry for the late reply, > Felix Lechner <[email protected]> > Over the years, Lintian accumulated many requests for features better > addressed by a shell script analyzer. If there are no objections, I > plan to assign them a copy each to morbig and shellcheck.
If I understood correctly, your intent is to create a wishlist bug to shellcheck, but I don't understand what would be the (active) role of shellcheck in this, could you clarify? > Paul Wise <[email protected]> > It also seems unlikely shellcheck would add a bridge between Haskell > and Perl of the kind needed to implement custom checks. I don't think such a thing is needed, shellcheck already provides multiple machine-readable output formats, which is the way IDEs integrate with it. Would you happen to be thinking about some usecase that is not covered by this? > Ralf Treinen <[email protected]> > what I can do is look through the bug reports blocked by #629247, > create whishlist bug reports for them on the lintshell project on gitlab I couldn't find this lintshell project, would you mind to give some references? It's the first time I'm hearing about it. To add to the general discussion, the way I envision this moving forward is that lintian integrates with linters (by their machine-readable outputs, just like IDEs) and calls them against the target files, with the possibility of ignoring checks that we might agree we don't want. Adding Debian specific checks would depend on a bunch of factors like: someone contributing directly to the linter tool, upstream accepting it, and the check per-se making sense to be upstreamed, but most importantly; providing Debian-specific checks would be a bonus, just by having plain shellcheck run by default on things like maintscripts would be a win. Regards, -- Samuel Henrique <samueloph>
