ready to be nuked. Even with LATEST_LINK set, both pkg_version and
portversion (from portuprade) were erroneously reporting an "upgrade"
from devel/autoconf->devel/autoconf253 and similarly for
automake->automake15.
These protocols are all used to run a remote session on a computer,
over a network. PuTTY implements the client end of that session:
the end at which the session is displayed, rather than the end
at which it runs.
WWW: http://www.chiark.greenend.org.uk/~sgtatham/putty/
Changelog:
- The "empty CC field" bug was fixed, as well as the
incorrect generation of SMTP headers.
- The application sets its icon now.
- A sysctl call is used instead of uname on BSD systems,
to avoid getting a truncated "uname -a" output.
Submitted by: Miguel Mendez <flynn@energyhq.es.eu.org> (maintainer)
PR: 62727
- sync parts of the Makefile with the sylpheed port
(LDAP/options/post-patch)
This update is a mix between my own update sitting in my tree since the
release of 0.9.9 (sorry, first I was busy, then I forgot about it) and
PR: 62774
Submitted by: lev
subnet, and that host is down/turned off, the Tnm::icmp echo command
will fail rather than return an unreachable indication on some
occasions. This is because the nmicmpd program will occasionally
get an EHOSTDOWN error when doing a sendto() when the ARP entry
resolution times out.
This is a problem since this API can support a list of hosts to
send traffic to, and a single error as described will abort the
entire operation.
(The reviewer claims that he could not duplicate the problem,
but that the patch seems like a good idea anyway.)
PR: ports/24940
Submitted by: Louis Mamakos <louie@transsys.com>
Reviewed by: Stefan Eßer <se@FreeBSD.org>
(commiter's note: verified) but the ownership changed from steve/steve
to skx/skx. The new distfile has a good PGP signature. Add downloading
of PGP signature.
PR: ports/62086
Submitted by: Jason Harris <jharris@widomaker.com>
postgresql-relay - multiplex all your databases to one point
of origin
postgresql-relay can be used to as a single point of origin
for all your databases. Instead of having to remember (or
modify in case of changes) all the names of your databases,
on which machines and on which ports they are running, you
only need to remember one machine and the name of the
database. The postgresql-relay will then forward the
connection to the proper database on the proper port of the
proper server. No more changes in the hundreds of clients
and scripts!
