pprkut / lintpkg Goto Github PK

It would be nice if we could run the testsuite with GitHub Actions. The challenge here is that (by default) GitHub Actions run on ubuntu. Running on Slackware would require a custom runner being hosted somewhere.
We can investigate, however, if we can get all the required dependencies available on a ubuntu system (pkgtools, primarily).
Another alternative would be trying to run the testsuite inside a Slackware docker container.

but I inserted one line and now it does:

--- lintpkg.orig 2017-01-20 12:15:41.699471760 +0000
+++ lintpkg 2017-01-20 13:19:24.493022010 +0000
@@ -437,6 +437,7 @@
PKG_LISTING=$(cat $PACKAGE | $packagecompression -dc | $TAR ts)
PKG_DETAILED_LISTING=$(cat $PACKAGE | $packagecompression -dc | $TAR tvs)

• PACKAGE=$( realpath $PACKAGE )
  cd $WORKING_DIR

  ( umask 000 ; cat $PACKAGE | $packagecompression -dc | $TAR xf - 2> /dev/null )

Currently info_check uses find to traverse the package contents to find directories named info, and potentially uncompressed info pages within them. We already have a list of the package contains though and going through that should be faster than searching on disk.

Incorporate the changes to pkgtools from pkgtools 15.0 (and newer). Most importantly:

• Change meaning of .tlz to tar.lz (lzip)
• If possible, use multiple decompression threads.
• Use recent tar, and support restoring POSIX ACLs and extended attributes.

Make the repository REUSE compliant and verify it using a GitHub action

Depends on #8

Currently man_check uses find to traverse the package contents to find directories named man, and potentially uncompressed man pages within them. We already have a list of the package contains though and going through that should be faster than searching on disk.

Not every rule is going to be universally applicable. There will always be room for exceptions. However, coding these exceptions directly into the lint checks isn't going to scale very well and may very well impact performance.
Instead, a way to let lintpkg know that a certain warning/error is not applicable is preferable. Still, they shouldn't be hidden completely. There should still be a way to see those warnings/errors, if one wants.

The override functionality from lintian is a pretty close match to that behavior. The idea would be to introduce a /usr/share/lintpkg/overrides directory holding override information per package. The content of such a file would look like this:

# Binary needs to retain debugging info to be useful:
foo: unstripped-binary /usr/bin/foo 

As a start, every file affected should be listed. We can introduce support for wildcards later.

Should be 'Existence' in README.md at 'Existance of an /install directory ...'

Add a GitHub Action that checks the repository for spelling mistakes using typos

Switch all files from noting the licensing inline to using SPDX license headers