(1) NOMANCOMPRESS is set by user, not porter. To indicate that MAN? variables
are referring to already compressed manpages, use MANCOMPRESSED.
(2) Remove second address from MAINTAINER line, I don't want anything to break.
slowdown problem.
Note, I've changed the DIST_SUBDIR.. all the patches files seem to be
called "fixes.patch" and were colliding with each other.
Reviewed by:
Submitted by:
Obtained from:
standards) quake101.zip. This reduces the sites to 3, but until Cracked.Com
releases a new version of the Linux Quake loader, there's not much more we
can do.
Submitted by: Tommy Cheng <tommycheng@pcmagic.net>
I think it's tonight, yeah
The release that's driving me mad
Is going out
She's got a cdrom to burn
She's got a cdrom to burn
She's got a cdrom to burn
But she don't care
[835 ports, in case you are wondering -- and "cvs co -D '3/18/97 01:10
PST'" will give you the ports tree for 2.2-RELEASE]
One thing added is being able to determin your domain name (as in FQDN)
at runtime by reading your /etc/resolv.conf file. Both "domain" and
"search" directives are supported.
One thing added is being able to determin your domain name (as in FQDN)
at runtime by reading your /etc/resolv.conf file. Both "domain" and
"search" directives are supported.
a) changed md5 checksum. original author made minor change but didn't
bump the version number - as usual :-(
b) knewsd isn't installed by default anymore, updated PLIST
(removed bin/knewsd and man/man1/knewsd.1.gz)
Now the port installs and packages well again !
Reviewed by:
Submitted by:
Obtained from:
2.2 (says Lars). I have now also moved freebsd_system.c out into a
files subdirectory, it used to be created in its entirety by patch-aa
before which makes maintenance fairly uncomfortable.
I have now verified that it builds and works with FreeBSD 2.1.x
(freefall -- it is really funny to watch it there, the disk transfers
and interrupts remain in the red zone all the time ;-), 3.0-current
(thud), and 2.2.
Submitted by: Lars_Koeller@odie.physik2.Uni-Rostock.DE
OKed by: asami
I'm trusting that this needs no approval during ports freeze because these
packages are not built automatically, so therefore this is not treading on
Satoshi's toes.
