pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2015-07-12	Expand ONLY_FOR_PLATFORM: the package internally thinks it supports	dholland	1	-2/+3
	Solaris, so enable that; and if it works on NetBSD and Dragonfly with a single "bsd" setting we can reasonably assume that it will work on FreeBSD and OpenBSD (and MirBSD and Bitrig) with only minor adjustments. These probably won't all quite work out of the box yet, but that's what bulk runs are for.
2012-10-23	Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.	asau	1	-3/+1

2011-03-21	simplify destdir support.	obache	1	-3/+4

2011-03-20	Add user-destdir installation support.	obache	1	-1/+5

2010-11-01	Reset maintainer.	wiz	1	-2/+2

2008-12-26	Make it work on DragonFly. Slightly modified patch from PR 40155.	hasso	1	-2/+2

2007-06-11	Bring this package closer to building under NetBSD 4.0:	tron	1	-2/+2
	- Escape some question marks to avoid weird GCC warning. - Fix broken use of "__attributed (__packed__)". Bump package revision because this is a code generation issue.
2006-02-05	Recursive revision bump / recommended bump for gettext ABI change.	joerg	1	-1/+2

2005-12-29	Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk	jlam	1	-2/+1
	automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-12-05	Fixed pkglint warnings. The warnings are mostly quoting issues, for	rillig	1	-3/+3
	example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
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-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-01-02	Initial import of pppd, version 2.4.3, into the NetBSD Package Collection.	cube	1	-0/+26
	The PPP Daemon is the userland part of the Point-to-Point Protocol. It works in combination with a dedicated kernel network interface usually named ppp. PPP is a very extensible protocol and pppd supports a large number of options, including compression (through various algorithms), cryptography (Microsoft's MPPE) and authentication (PAP, CHAP, Microsoft CHAP), provided the kernel has the relevant back-ends in some cases.