pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-12-15	Reset maintainer, ben@ has resigned.	wiz	1	-2/+2

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	-2/+2
	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).
2005-06-16	Create directories before installing files into them.	jlam	1	-1/+2

2005-04-09	Add buildlink3 file.	wiz	1	-0/+21

2005-04-05	Convert to bl3, untested.	wiz	1	-3/+2

2005-04-05	Sort.	wiz	1	-2/+2

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

2004-01-20	Move WRKSRC definition away from the first paragraph in a Makefile.	agc	1	-2/+3

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

2003-12-13	Update MAINTAINER email address.	ben	1	-2/+2

2003-12-13	Change from using packaged install program and flags, to a do-install	ben	1	-4/+5
	target in pkgsrc, in order to have a better chance of installing on Solaris and other platforms.
2003-12-11	Give these packages a higher chance to install on Solaris.	ben	1	-2/+2

2003-12-11	Update MASTER_SITES and HOMEPAGE to www.snake.net.	ben	1	-3/+3

2003-07-21	COMMENT should start with a capital letter.	martti	1	-2/+2

2003-07-19	Change address of maintainer per PR 22170.	wiz	1	-2/+2

2003-03-29	Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.	jmmv	1	-3/+2

2002-12-24	Replace collver@linuxfreemail.com with collver1@attbi.com.	wiz	1	-2/+2
	Closes PRs 19516, 19517, 19518, 19519, 19520, 19521, 19522, 19523, 19524, 19525 and some more, perhaps.
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	2	-1/+1

2001-04-27	Initial import of libmemmgr-1.04 into the packages collection.	agc	5	-0/+119
	Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com) MemMgr is a fairly trivial memory management library. There is little it does that cannot be done using routines in the C library. (In fact, allocation and disposal is implemented using C library routines.) The purposes of MemMgr are two- fold. (i) Minimize configuration burden on applications that dynamically allocate memory. For instance, malloc() on some systems returns a char pointer; on others it returns a void pointer. The MemMgr library routines encapsulate system-specific configuration differences and exports a fixed interface which is system-indepen- dent. Once you compile and install it, you just use it without thinking about whether your UNIX is System V or BSD inspired. (ii) Provide two parallel sets of allocation routines which either return NULL (for applications which want to check) or panic (for applications which simply want to die) on allocation failures. Panicking is implemented using the ETM library, which introduces a dependency on the ETM distribution. So be it. I use ETM for all my programs anyway