pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2013-05-23	prevent to generate binary package in ${PACKAGES} from the side effect of	obache	1	-1/+2
	`install' with USE_DESTDIR=yes. This changes prevent to unwanted overwite of existing binary packages with test installation (`stage-install', `replace' & `undo-replace', and so on). To do both `install' and `package', you can still use `package-install' target, same as USE_DESTDIR=no.
2010-02-24	Rename the install phase to stage-install. Introduce a new install	joerg	1	-2/+3
	target that defaults to either stage-install or package-install, depending on whether DESTDIR support is active and supported by the package or not.
2009-05-16	Don't require pkg_delete or pkg_info -r to list packages in full	joerg	1	-2/+7
	topological sort for the make update list. This breaks naturally when new dependencies are introduced that are also in the list scheduled for later installation. Reported by David Holland.
2008-02-07	Replaced _PKG_SILENT and _PKG_DEBUG with RUN.	rillig	1	-4/+4

2007-11-30	Since the "build" target is run inside the pkgsrc barrier, "build-env"	rillig	1	-2/+2
	gets the same treatment.
2007-08-31	Introduce a new target "checksum-phase" which is used as a dependency	jlam	1	-2/+2
	target by pkgsrc. This new target computes checksums only up until the extract phase is complete. The "checksum" target is now a target that can always be run by the user at any time, regardless of the presence of the work directory. These changes were proposed in PR pkg/36603 by Robert Elz.
2006-11-03	Add package-install. For non-DESTDIR builds, package and package-install	joerg	1	-1/+2
	are identical. For DESTDIR builds, the package is not installed to PREFIX as part of the build, so package-install does exactly that after package is done. Change bin-install to call package-install.
2006-10-06	Added a call similar to "make error-check" when the real target fails	rillig	1	-2/+14
	for some reason. That way, error and warning messages that have long been hidden are now shown. They don't appear very prominently by now, but it's much better than showing them not at all.
2006-07-27	Whenever we invoke a recursive make, we need to ensure that the proper	jlam	1	-2/+2
	environment ${PKGSRC_MAKE_ENV} is also passed along. Create a convenience variable RECURSIVE_MAKE that does exactly this and that can be used in place of MAKE when invoking make recursively. Use RECURSIVE_MAKE everywhere in pkgsrc/mk that we invoke make recursively.
2006-07-25	Move barrier to just after the depends phase. This allows both the	jlam	1	-3/+4
	"tools" and "wrapper" phases to be able to expect all the dependencies to be installed already.
2006-07-22	Modify the barrier so that we always invoke the recursive make process	jlam	1	-4/+4
	when passing through the barrier. This ensures the PATH (passed via PKGSRC_MAKE_ENV) is correctly set for all phases after the barrier. This fixes a bug in "interactive" pkgsrc use, where if you have no work directory and type "make build && make install", then the "install" step does not have a PATH set to include all the wrapper and tools directories.
2006-07-21	"BUILD_ENV" was misnamed. It's actually the environment that is passed	jlam	1	-2/+2
	to all internal recursive make processes. As such, rename it to "PKGSRC_MAKE_ENV". XXX Note, some of the usage of this variable in package Makefiles seems XXX incorrect. They probably want "MAKE_ENV", which is the environment XXX passed to the make process when running "make" within ${WRKSRC}.
2006-07-21	Rearrange sequence so that "wrapper" occurs between "tools" and	jlam	1	-2/+4
	"extract". This allows all user-definable targets (pre-, do-, post-*) to have access to the wrapper scripts.
2006-07-07	Rename <phase>_COOKIE variables to _COOKIE.<phase>. These are private	jlam	1	-6/+6
	variables so there are no user-visible changes. This change just makes it a little easier to write for loops.
2006-07-06	Remove an unnecessary target... ${_BARRIER_COOKIE} has no source targets	jlam	1	-5/+5
	so it might as well be the target name.
2006-07-06	The "replace" target does conceptually the same thing as the "install"	jlam	1	-4/+2
	target in that it installs the currently-built software into the filesystem. In that case where "replace" is specified as a target on the command line, make "replace" and not "install" be the source target for "package". Also, place the "replace" target between the "install" and "package" targets in _BARRIER_POST_TARGETS as it should be legal to do those steps in that order (but not in another order). These changes make the following work: make replace package In this example, the currently installed package will be replaced and the newly-installed software will be packaged, all within the same make process.
2006-07-06	Move inclusion of bsd.pkg.barrier.mk under the .MAIN target because	jlam	1	-1/+2
	bsd.pkg.barrier.mk uses the "make()" test expression. Also, include "all" as a post-barrier target since it is implicitly the ".MAIN" target when a user just types "make" in a package directory.
2006-07-06	Order the _BARRIER_POST_TARGETS so that if more than one is specified on	jlam	1	-17/+29
	the command-line, then we don't invoke make once for each target, and pass them to the sub-make in a sensible order.
2006-07-05	Flatten out recursive makes into a single re-invocation of make by	jlam	1	-0/+59
	introducing the concept of a "barrier". We separate the user-invokable targets into ones that must happen before the barrier, and ones that must happen after the barrier. The ones that happen after the barrier are run in a sub-make process. In this case, the targets that must be run after the barrier are from the "wrapper" step and beyond. We rewrite the various "flow" targets, e.g. wrapper, configure, build, etc., so that they of the right form to use the barrier target. This now completely removes the concept of PKG_PHASE from pkgsrc. It is replaced with the concept of "before" and "after" the barrier, and this state can be checked by testing for the existence of the barrier cookie file. Because we've removed most of the recursive makes, there is now nowhere to hook the PKG_ERROR_HANDLER.* commands, so remove them for now. As part of this commit, put back the logic that conditionalized the sources for the various cookie files. Because the sources are all "phony" targets, they were always run, regardless of whether or not the cookie file already existed. Now, if a cookie file exists, then that entire phase associated with that cookie file is skipped. Lastly, fix a thinko in configure/bsd.configure.mk where setting NO_CONFIGURE in a package Makefile would manage to skip the "wrapper" step altogether. Fix this by correctly noting "wrapper" and not "patch" as the preceding step to "configure".