I decided, not to choose the newest developement snapshot,
because it's a rapidly moving target and as you can see,
they doesn't store older SNAP's on their master site.
This would break the port every now and then and I don't
want to update the port on a daily or weekly basis (at least
it's a resource problem of time and money, this thing is too
big and expensive for me here in Germany).
-rw-r--r-- 1 59 59 4528325 Jan 10 15:33 ntp-4.0.91.tar.gz
^^
-rw-r--r-- 1 59 59 4552788 Jan 26 22:22 ntp-4.0.91d.tar.gz
^^ ^
Free Netware(tm) emulator (file/remote print/system binary server) written by
Martin Stover, porting to FreeBSD by Boris Popov (bp@butya.kz).
PR 9231
Submitted by: Boris Popov <bp@butya.kz>
Uses autoconf and libtool, now. Thus shared libraries are working now
and the bmakefiles are not necessary any longer.
OK'ed by: John Fieber <jfieber@FreeBSD.ORG>
crowded and I don't want to confuse cvsup about what's in
ports-base and what is not. (I.e., all uppercase
files/directories are, all lowercase ones are not.) While I'm
here, move the make_index script from templates to Tools.
(2) Adjust the MASTER_SITE_OVERRIDE logic a bit. Formerly, it was not
possible to specify both MASTER_SITE_OVERRIDE while still using
MASTER_SITE_BACKUP as a backup, as they were tied in the
implementation of MASTER_SITE_FREEBSD. You can now specify them
independently if MASTER_SITE_FREEBSD is not set (in which case
MASTER_SITE_BACKUP will be moved to the beginning of the list,
like before).
A utility for configuring sounds to play for WindowMaker events.
PR: 9184, 9566
Submitted by: Glenn Johnson <gljohns@bellsouth.net>,
Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
that is built. This saves a lot of time, especiall when the
parallelism (the number of jobs per machine, not the number of
machines) is low.
However, the build script only blows away /usr/local and
/usr/X11R6, so if there is a port that does some nasty things
outside that area, all bets are off.
(2) Better load balancing. Now, each machine reports its own
load in a form of a text file, which the master merely aggregates
to pick the lowest-loaded machine(s). Other than generally
running faster (and more up-to-date) under loaded conditions, the
master script will no longer hold up until a timeout when a
machine goes down.
