pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2008-02-07	Replaced _PKG_SILENT and _PKG_DEBUG with RUN.	rillig	1	-5/+5

2006-11-05	Normalized the way test(1) is used. Since I have no idea whether ${TEST}	rillig	1	-5/+5
	or [] is better, I have used [ to keep the code shorter. Noticed by wiz.
2006-11-05	The config.guess, config.sub and libtool files should also be	rillig	1	-5/+5
	overwritten when the package-provided files are (possibly dead) symlinks. Since on Mac OS X, ls(1) does not return the status I expected, I investigated a little in the available options of test(1), and found that the "-h" option should be quite portable. So let's try that instead. This fixes PR 34865.
2006-10-05	Replaced "test -f" with "ls". That way, broken symbolic links are also	rillig	1	-2/+2
	replaced with the pkgsrc versions of libtool, config.guess and others.
2006-07-19	Handle case where {SH,}LIBTOOL_OVERRIDE is empty for shells that don't	jlam	1	-3/+7
	understand empty lists in for loops. Addresses PR pkg/34042.
2006-07-19	Drop support for LTCONFIG_OVERRIDE. For quite a long time, pkgsrc	jlam	1	-36/+4
	had actually been ignoring LTCONFIG_OVERRIDE anyway and just using the default LIBTOOL_OVERRIDE to replace libtool scripts in packages. This just formalizes the fact that LTCONFIG_OVERRIDE is not used meaningfully by pkgsrc.
2006-07-07	LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE have slightly different	jlam	1	-13/+33
	semantics in pkgsrc. Because libtool-override is run by default whenever USE_LIBTOOL is specified, LIBTOOL_OVERRIDE never needs to be defined, and some packages set it to nothing to avoid running libtool-override. However, shlibtool-override is only run if SHLIBTOOL_OVERRIDE is defined and non-empty. Split the code for libtool-override and shlibtool-override to reflect these differing semantics. This should make the PHP packages build again by not overriding libtool.
2006-07-07	Move the STEP_MSG outside of the .if.endif block so it's always printed.	jlam	1	-3/+3

2006-07-07	Add missing "rm" statement that was causing the libtool wrapper to be	jlam	1	-1/+2
	overwritten in the case where LTCONFIG_OVERRIDE was defined. As a side note, after analyzing the way that the original code in bsd.pkg.mk worked, I think we can nuke LTCONFIG_OVERRIDE completely, but we'll need a bulk build to verify this. The original code always replaced the libtool scripts because LIBTOOL_OVERRIDE is always defined in bsd.pkg.use.mk, so LTCONFIG_OVERRIDE essentially had no effect.
2006-07-05	Refactor configure, build, test and wrapper phases out of bsd.pkg.mk	jlam	1	-0/+83
	and into their own directories. Also do some cleanups with build/_build and pkginstall -- we get rid of _build and simply run pkginstall as part of the "build" target. Introduce a new mechanism to handle varying directory depths under ${WRKSRC} in which we find files to override, e.g. configure, config., libtool, etc. OVERRIDE_DIRDEPTH is a package-settable variable that specifies how far under ${WRKSRC} the various targets should look, and it defaults to "2". We preserve the meaning of the various _OVERRIDE variables, so if they are defined, then their values supersede the OVERRIDE_DIRDEPTH mechanism. devel/tla will need to specially set OVERRIDE_DIRDEPTH to 3 (see log for revision 1.1857 for bsd.pkg.mk -- to be done in a separate commit.