pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2005-03-20	Remove useless buildlink3.mk file.	salo	1	-21/+0
	jabberd doesn't provide any libraries to link to.
2005-03-20	Backport fix for DoS attack in handling SSL connections from 1.4.3.	salo	3	-3/+33
	Bump PKGREVISION.
2004-12-28	The default location of the pkgsrc-installed rc.d scripts is now	reed	1	-2/+2
	under share/examples/rc.d. The variable name already was named RCD_SCRIPTS_EXAMPLEDIR. This is from ideas from Greg Woods and others. Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism (as requested by wiz).
2004-10-03	Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10	tv	1	-2/+2
	in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-05-07	Drop maintainership; I don't have the enough free time to maintain	xtraeme	1	-2/+2
	all these packages.
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-07	Fix CONFLICTS. (hi xtraeme!)	salo	1	-2/+2

2004-03-26	PKGREVISION bump after openssl-security-fix-update to 0.9.6m.	wiz	2	-2/+4
	Buildlink files: RECOMMENDED version changed to current version.
2004-03-18	Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly	jlam	1	-3/+2
	by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-05	Reorder location and setting of BUILDLINK_PACKAGES to match template	jlam	1	-10/+7
	buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-21	Downgrade jabberd to 1.4.2. Because 1.4.3 version doesn't work with	xtraeme	9	-206/+222
	current pth's version from pkgsrc. It was tested by David Ferlier <david@NetBSD-fr dot org> and it works perfectly, reported in PR pkg/24462.
2004-02-11	err it should be buildlink3.mk, sorry...	xtraeme	1	-1/+1

2004-02-11	Install some header files required to build jabberd related modules	xtraeme	3	-7/+34
	to the proper directory, add a missing buildlink3 file. Bump PKGREVISION.
2004-02-02	bl3ify and define u_int8_t=uint8_t.	grant	1	-4/+9
	fixes build on Solaris and with SunPro.
2004-01-22	replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.	grant	1	-2/+2

2003-12-23	Initial import of jabberd-1.4.3 from pkgsrc-wip.	xtraeme	9	-0/+327
	Jabber is an open XML protocol for real-time exchange of messages and presence notification between any two points on the Internet. The first application of Jabber technology is an asynchronous, extensible instant messaging platform, and an IM network that offers functionality similar to legacy IM systems such as AIM, ICQ, MSN, and Yahoo.