freebsd-ports-gnome - FreeBSD GNOME current development ports (https://github.com/freebsd/freebsd-ports-gnome)

	Commit message (Collapse)	Author	Age	Files	Lines
*	For ports maintained by ports@FreeBSD.org, remove names and/or	dougb	2009-12-21	1	-3/+1
\| \| \| \| \| \| \| \|	e-mail addresses from the pkg-descr file that could reasonably be mistaken for maintainer contact information in order to avoid confusion on the part of users looking for support. As a pleasant side effect this also avoids confusion and/or frustration for people who are no longer maintaining those ports.
*	truckman@ has had his port bit taken for safekeeping, therefore, return	linimon	2007-03-04	1	-1/+1
\| \| \| \| \| \|	this port to the pool. Hat: portmgr
*	Add SHA256.	truckman	2006-01-04	1	-0/+1
\|
*	Use DOCSDIR macro.	truckman	2004-03-18	2	-9/+8
\| \| \| \| \| \|	Install documents in DOCSDIR with INSTALL_DATA instead of INSTALL_MAN. Simplify executable and man page installation.
*	SIZEify.	truckman	2004-03-18	1	-0/+1
\| \| \| \|	Submitted by: trevor
*	Clear moonlight beckons.	ade	2003-03-07	2	-1/+1
\| \| \| \| \| \| \|	Requiem mors pacem pkg-comment, And be calm ports tree. E Nomini Patri, E Fili, E Spiritu Sancti.
*	Upgrade to version 1.3.	truckman	2002-06-24	7	-152/+11
\|
*	Fix broken link to coast.cs -> ftp.cerias.	will	2000-12-09	1	-1/+1
\| \| \| \|	Submitted by: Brian Poole <rajak@cerias.purdue.edu> (ftp.cerias admin)
*	Initialize supplementary groups.	truckman	2000-06-21	2	-0/+148
\| \| \| \| \| \| \|	Ensure that a LOG_NOTICE syslog is always generated when the program is invoked generated when the program is invoked an obvious error. Submitted by: Phil Pennock <phil@globnix.org>
*	Forgot to remove some variables	cpiazza	2000-04-10	1	-2/+0
\|
*	Update with the new PORTNAME/PORTVERSION variables	cpiazza	2000-04-10	1	-1/+3
\|
*	Respect CFLAGS	kris	2000-01-23	1	-0/+11
\|
*	The chrootuid command combines chroot(8) and su(1) into one program,	truckman	1999-12-09	6	-0/+59
	so that there is no need to have commands such as /usr/bin/su in the restricted environment. Access to the file system is restricted to the newroot subtree and privileges are restricted to those of the newuser account (which must be a known account in the unrestricted environment).