pkgsrc/net/tn5250/Makefile

# $NetBSD: Makefile,v 1.26 2018/01/14 10:41:37 wiz Exp $

DISTNAME=	tn5250-0.12.51
PKGREVISION=	5
CATEGORIES=	net
MASTER_SITES=	ftp://ftp.blarg.net/users/mmadore/

MAINTAINER=	pkgsrc-users@NetBSD.org
#HOMEPAGE=	http://www.linux-sna.org/software/5250/
COMMENT=	Implementation of the IBM 5250 telnet protocol

GNU_CONFIGURE=	YES
USE_LANGUAGES=	c c++
FAKE_NCURSES=	yes

LDFLAGS.SunOS+=	-lsocket -lnsl -lxnet

.include "../../mk/curses.buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
tn5250: comment out dead HOMEPAGE 2018-01-14 11:41:37 +01:00			`# $NetBSD: Makefile,v 1.26 2018/01/14 10:41:37 wiz Exp $`
Import of tn5250-0.12.51, an implementation of the IBM 5250 telnet protocol 1999-08-04 19:00:26 +02:00
			`DISTNAME= tn5250-0.12.51`
Use the curses framework. 2017-01-04 10:40:15 +01:00			`PKGREVISION= 5`
Import of tn5250-0.12.51, an implementation of the IBM 5250 telnet protocol 1999-08-04 19:00:26 +02:00			`CATEGORIES= net`
			`MASTER_SITES= ftp://ftp.blarg.net/users/mmadore/`

Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers. 2006-03-04 22:28:51 +01:00			`MAINTAINER= pkgsrc-users@NetBSD.org`
tn5250: comment out dead HOMEPAGE 2018-01-14 11:41:37 +01:00			`#HOMEPAGE= http://www.linux-sna.org/software/5250/`
Update to new COMMENT style: COMMENT var in Makefile instead of pkg/COMMENT. 2001-02-17 18:52:59 +01:00			`COMMENT= Implementation of the IBM 5250 telnet protocol`
Import of tn5250-0.12.51, an implementation of the IBM 5250 telnet protocol 1999-08-04 19:00:26 +02:00
buildlink1 -> buildlink2. 2002-10-25 19:51:44 +02:00			`GNU_CONFIGURE= YES`
Added "c" to USE_LANGUAGES for packages that use GNU configure scripts, since they always need a C compiler, even when the source code is completely in C++. For some other packages, stated in the comment that a C compiler is really not needed. 2006-07-22 06:46:13 +02:00			`USE_LANGUAGES= c c++`
Use the curses framework. 2017-01-04 10:40:15 +01:00			`FAKE_NCURSES= yes`
Uses C++. 2006-06-01 21:24:52 +02:00
Link network libs and include filio.h for FIONBIO on SunOS 2014-02-24 14:11:53 +01:00			`LDFLAGS.SunOS+= -lsocket -lnsl -lxnet`

Use the curses framework. 2017-01-04 10:40:15 +01:00			`.include "../../mk/curses.buildlink3.mk"`
Import of tn5250-0.12.51, an implementation of the IBM 5250 telnet protocol 1999-08-04 19:00:26 +02:00			`.include "../../mk/bsd.pkg.mk"`