1. xemacs
  2. xemacs-packages


xemacs-packages / INSTALL

                                             -*- Outline -*- 
This file covers building and installing XEmacs Package from CVS

	You MUST create a 'Local.rules' file in the toplevel build
	directory.  (see below for the format of this file)

* Building:
** Building Quickstart:

	(1) Create a 'Local.rules' file in the toplevel directory and
	    edit it to suit your needs.  There is a
	    'Local.rules.template' in the toplevel directory which you
	    can copy.

	(2) Regardless of the type of build you decide upon, it's
	    probably a good idea to run 'make autoloads' from the
	    toplevel directory. 

	(3) Run either 'make install' or 'make bindist' (not both).

	    'make install' builds the packages and installs them into
	    the $STAGING directory (see Local.rules format below).  It
	    doesn't create package binary tarballs.

	    'make bindist' builds the packages and creates package
	    binary tarballs and a 'package-index' file in $STAGING

** Building a Single Package:

	All you need to do is run the make from the package's
	directory.  Say, for example, you want to build the bbdb
	  	- cd ./comm/bbdb
		- make install or bindist

	You can build a category of packages just as easily.  For
	example, if you want to build all the packages in ./libs
		- cd ./libs
		- make install or bindist

** Building Sumo Packages:

	Get the script 'BuildSumo' that is in the xemacs-builds module
	at cvs.xemacs.org.

* Installing:
** Installing after a 'make install'

	I know that sounds odd, but if you set $XEMACS_STAGING and
	$MULE_STAGING to anything other than
	<emacs-roots>/lib/xemacs/xemacs-packages and
	<emacs-roots>/lib/xemacs/mule-packages respectively, you will
	need to either copy, move or symlink.

		- mkdir /usr/local/lib/xemacs/xemacs-packages
		- mkdir /usr/local/lib/xemacs/mule-packages
		- cd /usr/local/lib/xemacs/xemacs-packages
		- cp -a /path/to/$XEMACS_STAGING/* ./
		- cd ../mule-packages
		- cp -a /path/to/$MULE_STAGING/* ./
		- restart XEmacs.

** Installing after a 'make bindist'

	M-x pui-add-install-directory 
		- enter the value of $XEMACS_STAGING
	M-x package-get-update-base 
		- enter '$XEMACS_STAGING/package-index'
	M-x pui-list-packages
		- select the packages you want to install
		- hit 'x' to install
	Restart XEmacs.

** Installing - running "in place"

	You can't run XEmacs packages from the CVS source tree because
	the hierarchy is not what XEmacs expects.  But you can come
	close to a "running in place" install.

	Set the following in 'Local.rules':

	   - symlink = t
	   - XEMACS_STAGING = /usr/local/lib/xemacs/xemacs-packages
	   - MULE_STAGING = /usr/local/lib/xemacs/mule-packages

	And then run 'make install'.

	This will build the packages and install them via symlinks to
	the normal XEmacs package directories.

* Local.rules format:

These are the variables in 'Local.rules' that you will need to

	symlink = 
		Set this to 't' if you want to do a "run in place".
		Setting this doesn't work well with 'make bindist'

		This is where you set the normal packages that you
		want to install. eg:
			XEMACS_PACKAGES = libs/xemacs-base comm/bbdb

		Set this to where you want normal packages to be
		installed to.

	PACKAGE_INDEX = package-index
		If you want the package-index file to have a different
		name, change this.

		Building from CVS defaults to building the Mule
		packages.  Set this to 't' if you don't want/have Mule

		Same as for 'XEMACS_PACKAGES' except you list the Mule
		packages you want to install here. eg:
			MULE_PACKAGES = mule/mule-base mule/skk

		Set this to where you want Mule packages installed
		to.  Note:  'make bindist' does not use this variable.

	XEMACS = xemacs
		If your XEmacs isn't in your path, change this.

		Set this to 't' if you are building on WinNT.

	INSTALL = install -c
		The path to your BSD compatible install program.

	TAR = tar
		The path to your tar program

	BZIP2 =
		If you want bzip2 tarballs, set this.

	MAKEINFO = makeinfo
		The path to your makeinfo program

* Notes:
	(1) There have been a couple of reports that when you do an
	    initial check-out of the xemacs-packages module from CVS
	    sometimes the files 'Local.rules.template' & 'Local.rules.mk'
	    don't get checked out.  If this happens to you, try doing a
	    'cvs update'.  That should grab those files.