pkgsrc/pkgtools/xpkgwedge/pkg/DESCR
jlam e2ac9634c2 Update xpkgwedge to 1.0 and make appropriate changes to bsd.pkg.mk to handle
the new version of xpkgwedge.  Changes from xpkgwedge 0.4:

	* Redefine ImakeCmd to "imake -I$(PREFIX)/lib/X11/config" to
	  pick up X11 config files in $(PREFIX)/lib/X11/config before the
	  ones in the standard X11 tree.

	* Install a program called "pkgxmkmf" that's actually xmkmf, but
	  checks in $(PREFIX)/lib/X11/config before the standard X11 config
	  directory.

	* Create the host.def file in $(PREFIX)/lib/X11/config instead of
	  always in ${X11BASE}/lib/X11/config.

The benefits of this are:

	1) xpkgwedge can now install into $(PREFIX) instead of always into
	   $(X11BASE).

	2) Keeps the X11 tree "pure", and doesn't affect people who want
	   to run xmkmf and not include all the xpkgwedge stuff, even if
	   it's installed.

	3) Packages that install config files (lesstif, xview-config) can
	   now do so in $(PREFIX).

	4) People only have to use 'pkgxmkmf' instead of 'xmkmf', and
	   (hopefully) no other changes, if they want to use the config
	   files in xpkgwedge'd packages.
2000-10-23 17:32:06 +00:00

8 lines
487 B
Text

Xpkgwedge, not a "real" program in the traditional sense, is a hack that
allows NetBSD users to compile X11 pkgs from pkgsrc and install them
outside of the X11 tree - even if they use Imake - by using pkgxmkmf.
Pkgxmkmf is a slightly modified xmkmf from the X11R6.3 release and supports
finding config files in ${LOCALBASE}/lib/X11/config, if it exists, and in
${X11BASE}/lib/X11/config. In all other respects, it is identical to xmkmf.
Please refer to xmkmf(1) for more information.