Suggesting a check to remind maintainers to write up a good pkg-descr. A simple check for more than one sentence or more than one line might be sufficient to remind the maintainer to put a little more effort into it. Main aim would be to flag on-liners that may do an inadequate job describing the port according to the handbook standard: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-desc.html
ID
I'm sorry for the previous message. I wanted to say that maybe we should aim for a minimum of 3 lines as it's usually at least one sentence, one blank line and one line for a WWW address.
I was thinking the same, but would assume the URL line would be preprocessed out before checking the content, e.g. lines=`wc -l pkg-descr` head -n $((lines - 1)) | qc-command
Created attachment 192190 [details] Patch making portlint complain if pkg-descr is too short I'm submitting a patch (or at least a PoC) which makes portlint complain if pkg-descr is less than 3 lines. While here, I improved pkg-descr of portlint itself.
Committed to my repo pending the next release.
Committed, thanks!