pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-05-12	Add DragonFly support.	joerg	2	-9/+11

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.
2006-02-05	Recursive revision bump / recommended bump for gettext ABI change.	joerg	1	-1/+2

2005-12-05	Ran "pkglint --autofix", which corrected some of the quoting issues in	rillig	1	-2/+2
	CONFIGURE_ARGS.
2005-11-08	Use += in previous.	tv	1	-2/+2

2005-11-08	NOT_FOR_PLATFORM Interix.	tv	1	-1/+3

2005-05-22	Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:	jlam	1	-2/+2
	USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison
2005-02-24	Add RMD160 digests.	agc	1	-1/+2

2004-01-24	replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.	grant	1	-2/+2

2003-12-24	s/@netbsd.org/@NetBSD.org/ in MAINTAINER.	jmmv	1	-2/+2

2003-12-18	Initial import of rp-l2tp-0.3 into the NetBSD Packages Collection.	agc	12	-0/+231
	l2tpd is a user-space L2TP daemon. L2TP is the Layer Two Tunneling Protocol described in RFC 2661. It allows you to tunnel PPP sessions over a network or transport protocol (in this case, UDP.) Part of the l2tp code is implemented in the l2tpd program, and part of it is implemented as "handlers". A handler is a shared-object library which is dynamically linked into l2tpd at run-time using the "load-handler" configuration directive. Although the handlers included with this package (sync-pppd and cmd) are licensed under the GPL, as a special exception, you may write your own handlers which link to code in this package and not release them under the GPL. There may be other reasons why your handlers must be released under the GPL (for example, they may link with other GPL'd code), but in the absence of other reasons, you may keep your handlers proprietary.