pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2007-09-29	Documented the file format.	rillig	1	-1/+5

2007-05-07	Added variable descriptions.	rillig	1	-1/+5

2006-11-10	Provided the usual header comment.	rillig	1	-10/+20

2006-06-15	Pluralize INSTALL_TEMPLATE and DEINSTALL_TEMPLATE variable names as per	jlam	1	-3/+3
	the pkglint warning: As {INSTALL,DEINSTALL}_TEMPLATE is modified using "+=", its name should indicate plural. This does make the variables a bit more suggestive of the fact that they hold lists of values.
2006-03-14	Modify the pkginstall framework so that it manages all aspects of	jlam	1	-3/+3
	INSTALL/DEINSTALL script creation within pkgsrc. If an INSTALL or DEINSTALL script is found in the package directory, it is automatically used as a template for the pkginstall-generated scripts. If instead, they should be used simply as the full scripts, then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC explicitly, e.g.: INSTALL_SRC= ${PKGDIR}/INSTALL DEINSTALL_SRC= # emtpy As part of the restructuring of the pkginstall framework internals, we now always generate temporary INSTALL or DEINSTALL scripts. By comparing these temporary scripts with minimal INSTALL/DEINSTALL scripts formed from only the base templates, we determine whether or not the INSTALL/DEINSTALL scripts are actually needed by the package (see the generate-install-scripts target in bsd.pkginstall.mk). In addition, more variables in the framework have been made private. The _EXTRA_TMPL variables have been renamed to _TEMPLATE, which are more sensible names given the very few exported variables in this framework. The only public variables relating to the templates are: INSTALL_SRC INSTALL_TEMPLATE DEINSTALL_SRC DEINSTALL_TEMPLATE HEADER_TEMPLATE The packages in pkgsrc have been modified to reflect the changes in the pkginstall framework.
2005-12-29	Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk	jlam	1	-2/+1
	automatically detects whether we want the pkginstall machinery to be used by the package Makefile.
2005-01-25	Explicitly use -g to avoid relying on default behavior.	jmmv	1	-3/+3

2005-01-25	Redo previous per suggestion from reed@. Do not process the alternatives	jmmv	1	-21/+10
	until the pkg_alternatives package has been manually installed. This way we drop the dependency on that package.
2005-01-25	Make the usage of alternatives optional through the PKG_ALTERNATIVES variable,	jmmv	1	-6/+19
	which is similar to PKG_CONFIG. This does not change how the binary packages are built, only whether the pkg_alternatives command should be run at package installation/deinstallation time or not. The variable can take either YES or NO as values and defaults to YES.
2005-01-25	Add alternatives.mk, a file used to manipulate the alternatives system.	jmmv	1	-0/+56
	A package can optionally provide an ALTERNATIVES file which contains pairs of wrapper/alternative, one per line. The file is then used by the install and deinstall scripts to register the alternatives and to create the appropriate wrappers. Make bsd.pkg.mk include this new file. This happens unconditionally to keep all the alternatives logic in an independent file. Otherwise, some of the stuff could have to be moved to bsd.pkg.mk, breaking consistency.