pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	2	-1/+1

2001-10-22	Update HOMEPAGE and MASTER_SITES.	mycroft	1	-3/+3

2001-10-03	bsd.buildlink.mk will automatically handle the REPLACE_BUILDLINK stuff, so	jlam	1	-3/+1
	we can remove REPLACE_BUILDLINK settings containing -config, Conf.sh, and *.pc.
2001-10-03	Substitute the real config script for the config wrapper script in	jlam	1	-1/+3
	installed files. We don't want buildlink references to escape into the install directory.
2001-08-17	If USE_CONFIG_WRAPPER is defined (implied by USE_BUILDLINK_ONLY), then	jlam	1	-2/+3
	set FOO_CONFIG=${BUILDLINK_CONFIG_WRAPPER.foo} in both CONFIGURE_ENV and MAKE_ENV. We remove the check for GNU_CONFIGURE because if a package Makefile includes the buildlink.mk file, then it most likely wants to use the config script wrappers as well. Change suggested by Hubert Feyrer (hubertf) and Tomasz Luchowski (zuntum).
2001-07-27	Add dir_DEFAULT setting used by EVAL_PREFIX logic to set the default	jlam	1	-1/+2
	installation directory in case the package isn't installed.
2001-07-20	Mechanical changes to buildlink.mk files to use EVAL_PREFIX to set	jlam	1	-4/+6
	BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages regardless of whether they were installed before or after xpkgwedge was installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
2001-07-02	Allow overriding of *_CONFIG variables in a package Makefile when using	jlam	1	-2/+3
	USE_BUILDLINK_ONLY.
2001-07-01	Move inclusion of bsd.buildlink.mk to start of file.	jlam	1	-3/+3

2001-06-29	USE_CONFIG_WRAPPER is automatically set if USE_BUILDLINK_ONLY is defined,	jlam	1	-2/+1
	so remove it from package Makefiles. Also move the inclusion of the buildlink.mk files to the end of the Makefile to just before bsd.pkg.mk to ensure that any Makefile settings occur before the buildlink.mk files.
2001-06-26	Use REPLACE_BUILDLINK instead of repeating the post-build same code over	jlam	1	-14/+2
	and over again in the pkgsrc tree.
2001-06-23	Generalize how the dependency pattern may be specified. Instead of just	jlam	1	-4/+5
	FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib. Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS.
2001-06-19	Convert to use buildlink.mk files and mark as USE_BUILDLINK_ONLY. Refer to	jlam	3	-10/+34
	esd-config as $ESD_CONFIG in configure script.
2001-06-19	Add a buildlink.mk file for use by other package Makefiles.	jlam	1	-0/+41

2001-04-18	Move to sha1 digests, and add distfile sizes.	agc	1	-2/+3

2001-04-17	+ move the distfile digest/checksum value from files/md5 to distinfo	agc	2	-4/+2
	+ move the patch digest/checksum values from files/patch-sum to distinfo
2001-03-31	More cleanup of audio init code.	mycroft	2	-24/+42

2001-03-31	Samples are stored in the audio buffer in host order, not little-endian. Don't	mycroft	2	-4/+38
	generate static on big-endian machines. (Haven't I fixed this before??)
2001-03-31	Use /dev/sound, not /dev/audio.	mycroft	2	-25/+26

2001-02-16	Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT.	wiz	2	-2/+2

2001-01-04	The way that shared objects were handled in the PLISTs and bsd.pkg.mk was	agc	1	-1/+3
	out of date - it was based on a.out OBJECT_FMT, and added entries in the generated PLISTs to reflect the symlinks that ELF packages uses. It also tried to be clever, and removed and recreated any symbolic links that were created, which has resulted in some fun, especially with packages which use dlopen(3) to load modules. Some recent changes to our ld.so to bring it more into line with other Operating Systems also exposed some cracks. + Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain the ELF symlinks. + Don't mess about with file system entries when handling shared objects in bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will have got it right, and have a much better idea than we do. + Modify PLISTs to contain "ELF symlinks" + On a.out platforms, delete any "ELF symlinks" from the generated PLISTs + On ELF platforms, no extra processing needs to be done in bsd.pkg.mk + Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on a.out platforms + Update the documentation in Packages.txt With many thanks to Thomas Klausner for keeping me honest with this.
2000-10-13	Don't build threaded version just because "pth" happens to be installed	fredb	1	-1/+3
	on the build system.
2000-06-09	USE_LIBTOOL and LTCONFIG_OVERRIDE, instead of pkglibtool and patching	jlam	4	-39/+25
	configure.
2000-06-01	s/USE_LIBTOOL/USE_PKGLIBTOOL/	rh	1	-2/+2
	Add a new USE_LIBTOOL definition that uses the libtool package instead of pkglibtool which is now considered outdated. USE_PKGLIBTOOL is available for backwards compatibility with old packages but is deprecated for new packages.
2000-04-02	Update libmikmod to 3.1.9. Changes since 3.1.7 are numerous, see file NEWS	pooka	8	-31/+68
	included in the distribution for a complete list.
2000-03-07	Make sure that our package libtool is used.	tron	3	-3/+23

2000-03-07	Add missing "USE_GTEXINFO= YES".	tron	1	-4/+5

2000-02-06	wildcarded esound dependencies	wiz	1	-2/+2

1999-12-17	Update dependency on esound to reflect its correct version. Pointed	agc	1	-2/+2
	out by David Brownlee.
1999-12-10	The MikMod sound library is an excellent way for a programmer to	hubertf	8	-0/+102
	add music and sound effects to an application. It is a powerful and flexible library, with a simple and easy-to-learn API. Besides, the library is very portable and runs under a lot of Unices, as well as under OS/2, MacOS and Windows. Third party individuals also maintain ports on other systems, including MS-DOS, and BeOS. MikMod is able to play a wide range of module formats, as well as digital sound files. It can take advantage of particular features of your system, such as sound redirection over the network. And due to its modular nature, the library can be extended to support more sound or module formats, as well as new hardware or other sound output capabilities, as they appear. Submitted in PR 8543 by kuebart@mathematik.uni-ulm.de (Joachim Kuebart)