# $Id: README,v 1.2 2011/11/11 15:13:45 ksb Exp $

To install an entombing rm (and mv and cp) on a host you can do one
of three things:

On FREEBSD or so you can use the system source code with some make
recipe add-ons to rebuild the stock tools with -L/usr/local/lib -ltomb
to add the static code to from /usr/local/lib/libtomb.a to them.  On
a FreeBSD system that looks like
  # cd /usr/src/bin
  # (cd rm &&  make LDADD=-L/usr/local/lib\ -ltomb clean all install)
  # (cd cp &&  make LDADD=-L/usr/local/lib\ -ltomb clean all install)
  # (cd mv &&  make LDADD=-L/usr/local/lib\ -ltomb clean all install)

On a Linux system you must unpack the source RPMs and do about the
same thing (the LDADD macro might have changed there).


On a stricy GNU systemt that just uses the coreutils package as-is
you can use the spell encoded in the msrc structure to push coreutils
as a tar-blob, unpack it, configure it, hack the Makefile to include
entombing libs, and build/install that code.

On other systems you can replace /bin/rm with the coreutils one mostly,
as GNU rm is OK for every system but maybe AIX (IBMR2).


The technology behind the master source push is pretty clean, we use a
recipe (with the obvious depends) like this:
	+ if we don't have the "configure" script, unpack the source tar
	+ if we don't have a "config.h", run the configure script to make one
	+ if we don't have libfetish, make one
	+ for each of rm, mv, and cp:
		cd into the source to make them, then
		cp the new binary back to our build directory

--ksb, Nov 2011