by Ferenc Erki
Wikipedia defines linting software as:
a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs.
Linters play an important role to detect common mistakes fast. I often find that running them first in the build pipelines happens already too late, reducing their usefulness.
When to lint to maximize their value?
While I don’t write Go code, I do package Go projects for Gentoo Linux. My previous post about how to Host Gentoo dependency tarballs as GitHub releases got me invited to give a talk at the Google Developer Group Berlin Golang meetup, to host a community round table discussion at GopherCon Europe 2024, and to hold an online workshop for Gentoo e.V.
My presentation expands on the above post, and I decided to share the extra parts in this follow-up, including an idea for Go project maintainers who wish to streamline the distribution of their work.
st, “a simple terminal implementation for X”, has a new 0.9.2 release.
My overlay already makes it available for fellow Gentoo users. I also opened PR#36534 in the official Gentoo ebuild repository as proxied maintainer.
Clight describes itself as a “C daemon that turns your webcam into a light sensor”. My overlay has the latest v4.11 release available for fellow Gentoo users.
Vale, the “syntax-aware linter for prose built with speed and extensibility in mind”, has a new v3.4.2 release.
My overlay already makes it available for fellow Gentoo users. I also contributed the same ebuild to the official Gentoo GURU overlay, where it should reach the reviewed branch soon.