pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
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.
2006-04-12	Aligned the last line of the buildlink3.mk files with the first line, so	rillig	1	-2/+2
	that they look nicer.
2006-04-06	Over 1200 files touched but no revisions bumped :)	reed	1	-3/+3
	RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
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-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

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

2004-10-03	Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10	tv	2	-2/+4
	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-09-22	Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.	jlam	1	-5/+1
	All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-04-25	Convert to buildlink3.	snj	3	-39/+20

2004-04-16	update to 1.0	drochner	4	-33/+25
	changes: -more modular build (the pkg doesn't need glib anymore) -new oop_sys_run_once() function for polling
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.
2003-09-27	Initial import of liboop-0.9 into The NetBSD Packages Collection.	grant	5	-0/+106
	Liboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the "select() loop" and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application.