On Thursday 25 September 2014 23:37:24 David Spencer wrote:
TL;DR: Slackware package linter available at
https://github.com/pprkut/lintpkg
What, you mean like slackrepo --test ? :P
http://idlemoor.github.io/slackrepo/tests.html (out of date, I wrote
some more on a delayed train this
On Friday 26 September 2014 01:28:57 David Spencer wrote:
One observation -- some checks are easier, and much quicker, using awk
to read a verbose tar listing of the package instead of extracting a
full exploded package tree in the filestore. Very few checks will need
to examine file contents
Hello everyone!
TL;DR: Slackware package linter available at https://github.com/pprkut/lintpkg
Over the past couple of weeks I've been working on an idea I got some years
ago at FOSDEM. Other distributions have tools available to check the
correctness of created packages, like rpmlint or
TL;DR: Slackware package linter available at https://github.com/pprkut/lintpkg
What, you mean like slackrepo --test ? :P
http://idlemoor.github.io/slackrepo/tests.html (out of date, I wrote
some more on a delayed train this afternoon)
Comments, patches, pull requests are very welcome :)
This
On 9/25/14, Heinz Wiesinger ppr...@liwjatan.at wrote:
TL;DR: Slackware package linter available at
https://github.com/pprkut/lintpkg
Hey, this is nice! I've already got a couple ideas in mind for more checks...
___
SlackBuilds-users mailing list
One observation -- some checks are easier, and much quicker, using awk
to read a verbose tar listing of the package instead of extracting a
full exploded package tree in the filestore. Very few checks will need
to examine file contents (just slack-desc really). Are there reasons
I've missed for
