I'm really really really unhappy about these shared library patches.
This code changes WAY too fast to screw with shared libraries. If they
cause massive breakage again, they're history.
dynamically set it.
Suggested by: asami
Instead of explicitly specifying the path in MAKE_ENV, just retrieve it from
the env. var.
Move the comment about MAN1 var to the front of the variable definition.
Note from Vic:
There is a June 1 change to /usr/src/sys/sys/proc.h that lengthens the
proc structure. If you have updated your kernel sources, but haven't built
and installed a new kernel yet, then lsof report the open files belonging
to exactly one process, usually its own child process.
So, you'll either need to check out the previous copy of proc.h. Or
install that new kernel.
Explanation: this port used to use the Linux quake client in server mode. It now uses the BSD/OS dedicated server binary, which has lower CPU and memory footprint, and has a different version numbering scheme.
RUN_DEPENDS better reflects the reality instead of BUILD_DEPENDS.
Install doc files into ${LOCALBASE}/share/doc/pcb.
PR: 3689
Suggested by: mita@jp.freebsd.org
While at it,
List the man page and define MANCOMPRESSED.
Remove dhcpdb.bind file if changed dhcpdb.pool file.
If dhcpdb.pool file is changed and dhcpdb.bind file is
not matched to new pool file, dhcp server(dhcps) can not
run with some errors like this.
* dhcps in free(): warning: modified (chunk-) pointer.
* dhcps[25591]: hash_ins() with client identifier failed in read_bind_db()
I fixed start-up script to remove dhcpdb.bind file
when dhcpdb.pool file is newer than dhcpdb.bind.
Install intro.dhcp.jis file into ${PREFIX}/share/dhcp dirctory.
PR: 3717
Submitted-by: sanpei@yy.cs.keio.ac.jp
Unlink /etc/resolv.conf before recreate new one.
If /etc/resolv.conf is symbolic link file, dhcpc with -r
option overwrite symfile.
Then unlink it berfore recreate.
PR: 3717
Submitted-by: sanpei@yy.cs.keio.ac.jp
Append description into pkg/DESCR file.
o CHECK_SUM error problem under 2.1.x FreeBSD box.
o dhcps need dhcpdb.relay file without using dhcpdb.relay.
PR: 3717
Submitted-by: sanpei@yy.cs.keio.ac.jp
