pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2007-10-13	Fix the .include lines so that make looks in the right place first.	dsl	1	-2/+2
	Remember .include "foo.mk" is looked for (first) in the directory that contains the makefile being processed (like in C), so remove all the ${.PARSEDIR} and ../ sequences that just cause grief.
2007-08-14	Rewrote the header comment.	rillig	1	-11/+23

2006-11-04	Added BUILD_DEFS_EFFECTS.	rillig	1	-3/+3

2006-07-08	Change the format of BUILDLINK_ORDER to contain depth information as well,	jlam	1	-2/+2
	and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto
2006-07-08	Track information in a new variable BUILDLINK_ORDER that informs us	jlam	1	-1/+2
	of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2005-06-16	Use tabs, not spaces.	salo	1	-2/+2

2005-04-25	Add OS conditional blocks to exclude some PAM implementations from	tv	1	-2/+14
	selection, thus allowing "none" to be a correct result on systems where PAM is currently unavailable.
2005-01-14	Modify linux-pam and solaris-pam builtin.mk files to be more general	jlam	1	-2/+2
	in their tests for built-in versions of the PAM implementations. The MacOS X case now collapses nicely into the linux-pam case. Allow pam.buildlink3.mk to use solaris-pam as an accepted PAM implementation.
2005-01-14	We need to check that IS_BUILTIN.<pam> is "yes", not just that it's empty.	jlam	1	-2/+3

2005-01-14	Create a pam.buildlink3.mk file that is used by PAM-using packages.	jlam	1	-0/+76
	It includes the correct buildlink3.mk file from either Linux-PAM (security/PAM) or OpenPAM (security/openpam) and eventually will support solaris-pam. pam.buildlink3.mk will: * set PAMBASE to the base directory of the PAM files; * set PAM_TYPE to the PAM implementation used. There are two variables that can be used to tweak the selection of the PAM implementation: PAM_DEFAULT is a user-settable variable whose value is the default PAM implementation to use. PAM_ACCEPTED is a package-settable list of PAM implementations that may be used by the package. Modify most packages that include PAM/buildlink3.mk to include pam.buildlink3.mk instead.