pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2004-04-23	mk/bsd.pkg.install.mk now automatically registers	reed	1	-2/+1
	the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
2004-04-20	Apply a fix for anonymous auth_states in krb5.	recht	3	-3/+16
	Patch provided from Cyrus's CVS by Jukka Salmi in PR pkg/25256. Details: https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/cyrus/lib/auth_krb5.c.diff?r1=1.2&r2=1.3
2004-04-20	Give the user a chance to choice between db4/3 and remove BDB_DEFAULT	recht	1	-2/+1
	from the Makefile. Pointed out by Jukka Salmi.
2004-04-19	This only runs with db4/3. So, set BDB_ACCEPTED accordingly.	recht	1	-1/+3
	Fixes pkg/25247 by Jukka Salmi.
2004-03-29	Convert to use bdb.buildlink3.mk and krb5.buildlink3.mk.	jlam	1	-22/+39

2004-03-26	PKGREVISION bump after openssl-security-fix-update to 0.9.6m.	wiz	1	-1/+2
	Buildlink files: RECOMMENDED version changed to current version.
2004-02-14	Put post-install information into MESSAGE instead of using an INSTALL	snj	2	-13/+7
	script. Okayed by wiz.
2004-01-23	bl3ify	recht	1	-7/+7

2004-01-18	initial import of cyrus imapd 2.2.3	recht	17	-0/+625
	IMAP (Internet Message Access Protocol) is an Internet standards-track protocol for accessing messages (mail, bboards, news, etc). The Cyrus IMAP server differs from other IMAP server implementations in that it is generally intended to be run on "sealed" servers, where normal users are not permitted to log in. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP system. All user access to mail is through the IMAP, POP3, or KPOP protocols.