head	1.3;
access;
symbols;
locks; strict;
comment	@# @;


1.3
date	2003.02.27.07.27.47;	author jmallett;	state Exp;
branches;
next	1.2;

1.2
date	2002.06.30.23.32.02;	author jmallett;	state Exp;
branches;
next	1.1;

1.1
date	2002.06.30.01.17.49;	author jmallett;	state Exp;
branches;
next	;


desc
@@


1.3
log
@A simple build/install capability, allowing one to build something runnable
without hand-tchuning:
	make DESTDIR=/opt/source-code-control-system tree all install

Yes DESTDIR traditionally is used for engineering a release into a destination
dir, and it should probably be called PREFIX, as it is in code.  But bah,
humbug.  Spam the README with some of my own ranting, to accompany the
eloquent words Kirk wrote.

Notably, help doesn't work, unless you pull the help files from an SGI or
similar, and then you'll have the joy of "help stuck" and similar.  I'll try
to find a -free enough- source of these, though admittedly, that would require
being sure none of the errors mismatch, which would suck.

Still plenty of warning spa^H^H^H^H incentive.
@
text
@# $FreeBSD$

SUBDIR=	help sccs sccscmds
.if !defined(DESTDIR)
.error You did not set a DESTDIR, at least pass DESTDIR=/usr/local in
.endif

.include <bsd.subdir.mk>

DIRS=	bin lib lib/help man man/cat5 man/man1 man/cat1 share
.for _DIR in ${DIRS}
tree::
	-mkdir -p ${DESTDIR}/${_DIR}
.endfor
@


1.2
log
@Tie the repo copied `help' program into the build.
@
text
@d4 3
d9 6
@


1.1
log
@Add a top-level Makefile to drive the SCCS build.
@
text
@d3 1
a3 1
SUBDIR=	sccs sccscmds
@

