pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-05-21	Spell OPSYS as NetBSD as it is supposed to be.	joerg	1	-2/+2

2006-05-19	... I forgot to say: This update to 2.4.2 has mainly been done by Mark	rillig	1	-1/+1
	Kirby in PR 33515, with slight improvements by me.
2006-05-19	Updated cmake to 2.4.2.	rillig	5	-61/+128
	Since 2.0.5, there have been numerous small bug fixes, improvements in speed and portability.
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.
2006-02-05	Recursive revision bump / recommended bump for gettext ABI change.	joerg	2	-3/+4

2005-10-29	Add a Modules/Platform/DragonFly.cmake file (copied from FreeBSD.cmake).	reed	2	-3/+9
	cmake not tested on DragonFly, but did build package on DragonFly. Also hardcode "NetBSD" in PLIST instead of ${OPSYS} so deinstall works on non-NetBSD platforms. Bump PKGREVISION.
2005-10-24	Fixed the --mandir argument to configure. Makes the package build again on	rillig	1	-1/+3
	NetBSD-1.6.2/i386.
2005-10-23	Sorted PLISTs.	rillig	1	-2/+2

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-02-23	Add RMD160 digests.	agc	1	-1/+2

2005-01-06	Changes 2.0.5:	adam	3	-13/+14
	* Bug fixes
2004-12-03	Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.	wiz	1	-2/+2
	Suggested by Roland Illig, ok'd by various.
2004-10-03	Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10	tv	1	-1/+2
	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-10	add one...	drochner	1	-0/+21

2004-08-02	update to 2.0.2	drochner	6	-66/+66
	2.0 was a major feature release - too many to list here, see the included ChangeLog.* files for details. 2.0.x fixed bugs.
2004-02-10	bl3ify, and set USE_LANGUAGES appropriately	jlam	1	-10/+11

2004-02-02	fix wrong usage of ${OPSYS} in PLIST. fixes install on non-NetBSD.	grant	2	-4/+4
	bump PKGREVISION.
2004-01-22	replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.	grant	1	-2/+2

2003-12-30	Add trailing / on HOMEPAGEs	cjep	1	-2/+2

2003-09-28	Back out last change related to moving ncurses/buildlink2.mk to	jlam	1	-2/+2
	curses.buildlink2.mk. This was wrong because we _really_ do want to express that we want _n_curses when we include the buildlink2.mk file. We should have a better way to say that the NetBSD curses doesn't quite work well enough. In fact, it's far better to depend on ncurses by default, and exceptionally note when it's okay to use NetBSD curses for specific packages. We will look into this again in the future.
2003-09-27	move ncurses/buildlink2.mk to mk/curses.buildlink2.mk, as it provides	grant	1	-2/+2
	support for base system curses/ncurses as well as ncurses itself. suggested by wiz.
2003-07-21	COMMENT should start with a capital letter.	martti	1	-2/+2

2003-07-17	s/netbsd.org/NetBSD.org/	grant	1	-2/+2

2003-07-13	PKGREVISION bump for libiconv update.	wiz	1	-1/+2

2003-06-02	Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.	jschauma	1	-2/+2
	Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2003-05-07	import cmake-1.6.6	dmcmahill	7	-0/+264
	CMake is an extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Simple configuration files placed in each source directory (called CMakeLists.txt files) are used to generate standard build files (e.g., makefiles on Unix and projects/workspaces in Windows MSVC) which are used in the usual way. CMake can compile source code, create libraries, generate wrappers, and build executables in arbitrary combinations. CMake supports in-place and out-of-place builds, and can therefore support multiple builds from a single source tree. CMake also supports static and dynamic library builds. Another nice feature of CMake is that it generates a cache file that is designed to be used with a graphical editor. For example, when CMake runs, it locates include files, libraries, and executable, and may encounter optional build directives. This information is gathered into the cache, which may be changed by the user prior to the generation of the native build files.