pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-03-04	Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no	jlam	1	-2/+2
	developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-11-07	Pull in libbind resolver on Interix.	tv	1	-0/+11

2005-06-17	Create directories before installing files into them.	jlam	1	-1/+2

2005-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-02-24	Add RMD160 digests.	agc	1	-1/+2

2005-02-21	Sign over maintainership to tech-pkg@	hubertf	1	-2/+2

2004-12-21	Update DHIS server to 5.1, per PR pkg/28704.	hubertf	3	-11/+10
	Changes: AUTH_ACK packets return the client's external interface IP address for its possible use.
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-04-25	Convert to buildlink3 and correct two spelling errors in DESCR.	snj	2	-5/+5

2004-01-11	Remove inclusion of varargs.h as the program does not appear to use	cjep	4	-10/+20
	va_{start,arg,end} and the inclusion stops the program building with gcc3.3. (Also use bl2.)
2003-12-30	Add trailing / to HOMEPAGEs	cjep	1	-2/+2

2003-07-17	s/netbsd.org/NetBSD.org/	grant	1	-2/+2

2002-04-11	Improve gmp wildcard to be happy with 4.0.1.	wiz	1	-2/+2

2001-12-05	s/root/${ROOT_USER}/g, now that the definition appears in the	agc	1	-2/+2
	defs.${OPSYS}.mk files.
2001-10-31	Move pkg/ files into package's toplevel directory	zuntum	2	-1/+1

2001-06-05	Import dhisd-5.0: DynDNS server	hubertf	6	-0/+113
	By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.