freebsd-ports/devel/gnu-autoconf/Makefile

# New ports collection makefile for:	autoconf
# Version required:     2.12
# Date created:		7 October 1995
# Whom:			torstenb@FreeBSD.ORG
#
# $Id: Makefile,v 1.11 1997/06/13 07:33:36 max Exp $
#

DISTNAME=       autoconf-2.12
CATEGORIES=	devel
MASTER_SITES=	${MASTER_SITE_GNU}

RUN_DEPENDS=	gm4:${PORTSDIR}/devel/m4

MAINTAINER=	torstenb@FreeBSD.ORG

GNU_CONFIGURE=	yes
CONFIGURE_ENV=	M4=${PREFIX}/bin/gm4

post-install:
	@if [ ! -f ${PREFIX}/info/dir ]; then \
	  ${SED} -ne '1,/Menu:/p' /usr/share/info/dir > ${PREFIX}/info/dir; \
	 fi
	@install-info ${PREFIX}/info/autoconf.info ${PREFIX}/info/dir
	@install-info ${PREFIX}/info/standards.info ${PREFIX}/info/dir

.include <bsd.port.mk>
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00			`# New ports collection makefile for: autoconf`
upgrade to 1.12 Submitted by: fenner 1997-01-16 10:11:39 +00:00			`# Version required: 2.12`
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00			`# Date created: 7 October 1995`
			`# Whom: torstenb@FreeBSD.ORG`
			`#`
sed -> ${SED} Add `@' at the beginning of install-info related commands in post-install. 1997-06-13 20:00:47 +00:00			`# $Id: Makefile,v 1.11 1997/06/13 07:33:36 max Exp $`
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00			`#`

upgrade to 1.12 Submitted by: fenner 1997-01-16 10:11:39 +00:00			`DISTNAME= autoconf-2.12`
Change gategory name "development" -> "devel". Also take out the "programming" that was in some of them, it's pretty obvious what we are talking about here. 1995-11-26 11:29:21 +00:00			`CATEGORIES= devel`
Use MASTER_SITE_GNU Use MAN? macros. CATEGORIES+= -> CATEGORIES. 1996-11-18 10:25:35 +00:00			`MASTER_SITES= ${MASTER_SITE_GNU}`
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00
Use RUN_DEPENDS instead of EXEC_DEPENDS, as it is not (technicall) necessary to have /usr/local/bin/gm4 just to build this port. However, the configure script would find /usr/bin/m4 if /usr/local/bin/gm4 isn't there, so tell it to use tha latter via CONFIGURE_ENV. 1996-04-01 05:09:13 +00:00			`RUN_DEPENDS= gm4:${PORTSDIR}/devel/m4`
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00
			`MAINTAINER= torstenb@FreeBSD.ORG`

			`GNU_CONFIGURE= yes`
Use RUN_DEPENDS instead of EXEC_DEPENDS, as it is not (technicall) necessary to have /usr/local/bin/gm4 just to build this port. However, the configure script would find /usr/bin/m4 if /usr/local/bin/gm4 isn't there, so tell it to use tha latter via CONFIGURE_ENV. 1996-04-01 05:09:13 +00:00			`CONFIGURE_ENV= M4=${PREFIX}/bin/gm4`
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00
Use install-info to add info dir entry. 1997-06-13 07:33:36 +00:00			`post-install:`
sed -> ${SED} Add `@' at the beginning of install-info related commands in post-install. 1997-06-13 20:00:47 +00:00			`@if [ ! -f ${PREFIX}/info/dir ]; then \`
			`${SED} -ne '1,/Menu:/p' /usr/share/info/dir > ${PREFIX}/info/dir; \`
Use install-info to add info dir entry. 1997-06-13 07:33:36 +00:00			`fi`
sed -> ${SED} Add `@' at the beginning of install-info related commands in post-install. 1997-06-13 20:00:47 +00:00			`@install-info ${PREFIX}/info/autoconf.info ${PREFIX}/info/dir`
			`@install-info ${PREFIX}/info/standards.info ${PREFIX}/info/dir`
Use install-info to add info dir entry. 1997-06-13 07:33:36 +00:00
GNU autoconf ver 2.4, to generate your own configure scripts. Submitted by: torstenb 1995-10-12 07:11:56 +00:00			`.include <bsd.port.mk>`