portlint port passing portlint)
New portlint features:
* Allow pkg/COMMENT to start with a digit
* Warn about .la files in pkg/PLIST
* Better support for comments in the Makefile
- fixes the section off by 1 error
(DISTNAME needs to exist, and so on, when it does)
* don't report "FATAL: no MAINTAINER listed in Makefile" when it does exist
* other random minor bug fixes
- enforce pkg/COMMENT style
- better info file checking in pkg/PLIST
- don't warn about @unexec rmdir foo || true - the handbook says this is fine
- allow CATEGORIES+=
- warn about www.freebsd.org/~user needing to be people.freebsd.org
- warn about PKGNAME being set from another variable instead of being a
fatal error
- understand both $(PORTSDIR) and ${PORTSDIR}
[Has anyone figured-out what makes the number 393 so interesting to PW, now?]
I wonder what was going through Jordan's head during his infamous
$Id$-smashing commit.
Before I forget....
Thanks to naddy@mips.rhein-neckar.de (Christian Weisgerber) for prompting
this commit. See msg-id: 7geokh$tje$1@mips.rhein-neckar.de
put the source code for "portlint" into FreeBSD port tree. The
imported revision is 1.65 (in my local RCS file). (pseudo) version
number for the port is now 2.0.
Whoever make changes to bsd.port.mk is advised to update portlint.pl
too :-)
Note that portlint.pl MUST be portable enough to handle (Net|Open|Free)BSD
bsd.port.mk. There are people using portlint.pl on non-FreeBSD
platforms.
Portcheckout(1) checks out a FreeBSD port and all runtime
and buildtime depending ports into the current working
directory. The output is written to stdout as an
executable shell-script.
Compiling a FreeBSD port usually require a full tree of ports
in /usr/port. A cvs checkout or a cvs update command takes
a very long time and need much free space.
With portcheckout, you checkout only the parts of the port
tree which you really need. This is a magnitude faster!
but aren't in a tk virtual category from
awk -F\| '$9 ~ /tk-/ && $7 !~ /tk/ {print $1}' INDEX
I didn't do anything about the ports which depend on things which depend
on a tk revision. I'd be afraid that the depended-upon port might change
and thus outdate the virtual category in the depender.
