>Date: Wed, 3 Jan 1996 05:19:53 +0100
>From: Hubert Feyrer <Hubert.Feyrer@rz.uni-regensburg.de>

>Think of the poor guy putting a package together: he types 'make install', and
>gets files spilled all over his file-system if he uses the usual
>"default"-setup. Now pkg_tools demands a list of files to include in the
>package... how should he know? Not easy, and the main reason I didn't use
>pkg_tools.

A little ingenuity helps.  For instance, anything that uses GNU
autoconf lets you select the installation directory prefix.  All you
have to do is create an empty /tmp/pkg,

make install prefix=/tmp/pkg
(cd /tmp/pkg; find . -type f -print) > package.pkg

and you're mostly there.

John Kohl sent me the makefile below; I've used it as a starting point
to create the packages I've uploaded:

#	$Id: Makefile,v 1.4 1995/01/25 01:32:39 jtkohl Exp $	
PCR=/usr/local/sbin/pkg_create
CREATE=$(PCR) -v -t /build/jtk/instmp.XXXXXX

PACKAGES=emacs-19.tgz

all: MD5SUMS
MD5SUMS: *.README $(PACKAGES)
	md5 $> >MD5SUMS

.SUFFIXES: .pkl .pklm .pkg .tgz

# PKL has a display/LEGAL file
.pkl.tgz: $*.README $*.oneline $*.LEGAL
	name=`cat $*.oneline`;  \
	echo $(CREATE) -d $*.README -f $*.pkl -c -'"'$$name'"' -D $*.LEGAL $* | $(SHELL)

# PKLM has a display/LEGAL file and an mtree file
.pklm.tgz: $*.README $*.oneline $*.LEGAL $*.mtree
	name=`cat $*.oneline`;  \
	echo $(CREATE) -d $*.README -f $*.pklm -m $*.mtree -c -'"'$$name'"' -D $*.LEGAL $* | $(SHELL)

# PKG has no associated display/LEGAL file
.pkg.tgz: $*.README $*.oneline
	name=`cat $*.oneline`;  \
	echo $(CREATE) -d $*.README -f $*.pkg -c -'"'$$name'"' $* | $(SHELL)

-- 
Mike Long <mike.long@analog.com>           http://www.shore.net/~mikel
VLSI Design Engineer         finger mikel@shore.net for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA       (eq (opinion 'ADI) (opinion 'mike)) -> nil