A ports freeze means that commits will be few and far between and only by approval.

Number of commits found: 18

Remove all stalled Makefiles in net category.

Approved and reviewed by:       marcus

De-pkg-comment.

Update to version 2.0.1
freebsd.org -> FreeBSD.org
Adjust pkg-descr

PR:     43457

Oops. You need to install *both* kinds of configurator. Which you use
depends on which version of the airport ("graphite" or "snow") you own.

1. Update to 2.0

2. Use new java port infrastructure.

3. Since we require swing, we require Java 1.2+. This also simplifies
the script, since we can presume 'javavm -jar foo.jar' will work.

The latest version unzips to a subdir.    

Update to 1.5.2 and 1.4    

Release this port, as I no longer have a real Airport anymore.    

Upgrade configurator to v1.5.    

1. Add the modem connect/hangup utility, since the author has provided a  
version numbered distfile.    

Add support for the Airport Host and Link monitors. The port won't be   able to
track the version numbers of those, but if they increment before   the
configurator does, we can use PORTREVISION. We'll bump that now too,   of
course. We can't add the modem utility because there isn't a distfile  
available that has a version number in it. :-(    

Take a hint from the mindterm port -- JAR files go in   share/java. Everything
else in share/doc. Bump PORTREVISION.    

Make the default installation work. Add an alternative to the shell   script for
those who've installed a Java 2 VM. Life will be   exponentially better when we
can count on 'javavm -jar foo.jar' just   doing The Right Thing(tm).    

Update to v1.4    

Use the javavmwrapper rather than explicitely naming the jdk.    

Update to v1.3 finally.    

1. Update to 1.2.2    

Add port for java airport configurator    

Number of commits found: 18

14 vulnerabilities affecting 30 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities