# Automated linting What do people think about automating package linting? This would be to make sure a package is linted before it is committed to the Guix repository master branch?
I am not familiar with what Guix uses for continuous integration / deployment. I do not know if automated linting is already in place. The packages on the master branch that have linting issues could have been committed before automated linting was in place. # Acknowledgment It was brought to my attention by Tobias Geerinckx-Rice: "... tarballs aren't guaranteed to be stable over time (GitHub can regenerate them, changing the metadata and hence the hash, and has done so in the past). They must not be used. ..." https://lists.gnu.org/archive/html/help-guix/2019-03/msg00096.html # Guix master branch There are package in the Guix repository master branch that use an autogenerated tarball and have this lint output: "the source URI should not be an autogenerated tarball" # Number of packages Estimated number of packages with autogenerated tarball: 389 This is a low estimate as it is only counts GitHub autogenerated tarballs. This estimate is from this command run in the Guix repository. `grep github.*archive gnu/packages/*scm | wc -l`
