pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
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	-3/+5
	buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-14	PKGCONFIG_OVERRIDE is relative to WRKSRC.	jmmv	1	-2/+2

2004-02-14	LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globs	jlam	1	-2/+1
	relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-01-24	Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. In	jlam	1	-5/+4
	the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched.
2004-01-17	remove references to work dir (S/.work//)	recht	2	-4/+4

2004-01-17	initial import of libcddb-0.9.4	recht	6	-0/+86
	Libcddb is a library that implements the different protocols (CDDBP, HTTP, SMTP) to access data on a CDDB server (http://freedb.org). It tries to be as cross-platform as possible. The initial libary will have a C API.