doc/en_US.ISO8859-1/Makefile

#       $Id: Makefile,v 1.4 1999-08-26 19:42:10 nik Exp $

SUBDIR = articles
SUBDIR+= books

COMPAT_SYMLINK = en

#
# Put the compatability symlink in place.
#
afterinstall:
.if !defined(IGNORE_COMPAT_SYMLINK)
	if [ ! -e ${DOCDIR}/${COMPAT_SYMLINK} ]; then			\
		rm -rf ${DOCDIR}/${COMPAT_SYMLINK};			\
		(cd ${DOCDIR} && ln -s en_US.ISO_8859-1 ${COMPAT_SYMLINK}); \
	fi
.endif

.include <bsd.subdir.mk>

DOC_PREFIX?= ..
.include "../share/mk/docproj.docbook.mk"
When making the compatability symlink, do it in the parent directory to both directories, and make it relative, rather than absolute. This fixes the case where you might install the docs under one directory /foo/bar/..., and then want to migrate them elsewhere (to /usr/share/). With the old scheme, the symlink would start /foo/bar/..., and would therefore be broken. A good example of this happening is "make release" :-) 1999-08-26 21:42:13 +02:00			`# $Id: Makefile,v 1.4 1999-08-26 19:42:10 nik Exp $`
New Makefile -- just points to the handbook/ subdirectory for now. 1999-03-08 22:43:32 +01:00
The new Makefile framework. Does the right thing (pretty much) except in the case of */FAQ/Makefile, because the FAQs are all in the wrong place. Things still install properly, but some of the directory paths are hardcoded. This will be going away ASAP. 1999-08-17 00:09:20 +02:00			`SUBDIR = articles`
			`SUBDIR+= books`

			`COMPAT_SYMLINK = en`

			`#`
			`# Put the compatability symlink in place.`
			`#`
			`afterinstall:`
			`.if !defined(IGNORE_COMPAT_SYMLINK)`
Honour ${DOCDIR} when installing the documentation. 1999-08-19 22:36:02 +02:00			`if [ ! -e ${DOCDIR}/${COMPAT_SYMLINK} ]; then \`
			`rm -rf ${DOCDIR}/${COMPAT_SYMLINK}; \`
When making the compatability symlink, do it in the parent directory to both directories, and make it relative, rather than absolute. This fixes the case where you might install the docs under one directory /foo/bar/..., and then want to migrate them elsewhere (to /usr/share/). With the old scheme, the symlink would start /foo/bar/..., and would therefore be broken. A good example of this happening is "make release" :-) 1999-08-26 21:42:13 +02:00			`(cd ${DOCDIR} && ln -s en_US.ISO_8859-1 ${COMPAT_SYMLINK}); \`
The new Makefile framework. Does the right thing (pretty much) except in the case of */FAQ/Makefile, because the FAQs are all in the wrong place. Things still install properly, but some of the directory paths are hardcoded. This will be going away ASAP. 1999-08-17 00:09:20 +02:00			`fi`
			`.endif`
New Makefile -- just points to the handbook/ subdirectory for now. 1999-03-08 22:43:32 +01:00
			`.include <bsd.subdir.mk>`
Honour ${DOCDIR} when installing the documentation. 1999-08-19 22:36:02 +02:00
			`DOC_PREFIX?= ..`
			`.include "../share/mk/docproj.docbook.mk"`