Juergen Daubert wrote:
Hi all,
based on Johannes' ideas and performance specification [1] I've written a simple utility, called portverify, to check CRUX ports for typical errors. It's a shell script which calls gawk with a bunch of small scripts, each of them containing one or more tests.
Following test are implemented yet:
- port - missing files Pkgfile/.footprint/.md5sum - Pkgfile - existence of name/version/release/source variables - match of portname to name variable - wrong release number - cd/rm command outside the work directory - .footprint - world writable files/directories - junk files like perllocal.pod - invalid directories like /usr/info - invalid users - files not owned by root - SUID/SGID files
Pretty cool. As I read this at 7am with my eyes half open, I thought you were announcing "poverty," and I started to feel bad for you. Maybe we can call it poverty for short? -- Jay Dolan jdolan.dyndns.org A: Because it's difficult to read. Q: Why is top-posting bad? A: Top posting. Q: What's the most annoying thing about usenet?