Add port sysutils/tm:
Terminal mixer can start processes inside a pseudo-terminal, which can
be accessed through a Unix socket, TCP or even raw ethernet (not yet
ported to FreeBSD). The programs can be linked to the current
terminal, or they can be unlinked like in nohup. But even in this
latter case you can connect to them using the mentioned protocols.
tm can also start programs as if they communicate through pipes
instead of terminals, and this can be quite useful for
remote-controlling applications.
More than one client can connect to the served pseudo-terminal, either
using tm as a client or telnet for TCP. You can choose if they are
only allowed to read, or they can also contribute on input.
WWW: http://vicerveza.homeunix.net/~viric/soft/tm/
Author: Lluis Batlle i Rossell <viric_at_vicerveza_dot_homeunix_dot_net>
Terminal mixer can start processes inside a pseudo-terminal, which can
be accessed through a Unix socket, TCP or even raw ethernet (not yet
ported to FreeBSD). The programs can be linked to the current
terminal, or they can be unlinked like in nohup. But even in this
latter case you can connect to them using the mentioned protocols.
tm can also start programs as if they communicate through pipes
instead of terminals, and this can be quite useful for
remote-controlling applications.
More than one client can connect to the served pseudo-terminal, either
using tm as a client or telnet for TCP. You can choose if they are
only allowed to read, or they can also contribute on input.
WWW: http://vicerveza.homeunix.net/~viric/soft/tm/
Author: Lluis Batlle i Rossell <viric_at_vicerveza_dot_homeunix_dot_net>
2007-12-18 16:44:11 +01:00
|
|
|
# New ports collection makefile for: tm
|
|
|
|
|
# Date created: 18 December 2007
|
|
|
|
|
# Whom: Andrew Pantyukhin <infofarmer@FreeBSD.org>
|
|
|
|
|
#
|
|
|
|
|
# $FreeBSD$
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
PORTNAME= tm
|
2008-05-03 21:06:02 +02:00
|
|
|
PORTVERSION= 0.4.1
|
Add port sysutils/tm:
Terminal mixer can start processes inside a pseudo-terminal, which can
be accessed through a Unix socket, TCP or even raw ethernet (not yet
ported to FreeBSD). The programs can be linked to the current
terminal, or they can be unlinked like in nohup. But even in this
latter case you can connect to them using the mentioned protocols.
tm can also start programs as if they communicate through pipes
instead of terminals, and this can be quite useful for
remote-controlling applications.
More than one client can connect to the served pseudo-terminal, either
using tm as a client or telnet for TCP. You can choose if they are
only allowed to read, or they can also contribute on input.
WWW: http://vicerveza.homeunix.net/~viric/soft/tm/
Author: Lluis Batlle i Rossell <viric_at_vicerveza_dot_homeunix_dot_net>
Terminal mixer can start processes inside a pseudo-terminal, which can
be accessed through a Unix socket, TCP or even raw ethernet (not yet
ported to FreeBSD). The programs can be linked to the current
terminal, or they can be unlinked like in nohup. But even in this
latter case you can connect to them using the mentioned protocols.
tm can also start programs as if they communicate through pipes
instead of terminals, and this can be quite useful for
remote-controlling applications.
More than one client can connect to the served pseudo-terminal, either
using tm as a client or telnet for TCP. You can choose if they are
only allowed to read, or they can also contribute on input.
WWW: http://vicerveza.homeunix.net/~viric/soft/tm/
Author: Lluis Batlle i Rossell <viric_at_vicerveza_dot_homeunix_dot_net>
2007-12-18 16:44:11 +01:00
|
|
|
CATEGORIES= sysutils
|
|
|
|
|
MASTER_SITES= http://vicerveza.homeunix.net/~viric/soft/tm/ CENKES
|
|
|
|
|
|
2008-09-07 02:19:05 +02:00
|
|
|
MAINTAINER= ports@FreeBSD.org
|
Add port sysutils/tm:
Terminal mixer can start processes inside a pseudo-terminal, which can
be accessed through a Unix socket, TCP or even raw ethernet (not yet
ported to FreeBSD). The programs can be linked to the current
terminal, or they can be unlinked like in nohup. But even in this
latter case you can connect to them using the mentioned protocols.
tm can also start programs as if they communicate through pipes
instead of terminals, and this can be quite useful for
remote-controlling applications.
More than one client can connect to the served pseudo-terminal, either
using tm as a client or telnet for TCP. You can choose if they are
only allowed to read, or they can also contribute on input.
WWW: http://vicerveza.homeunix.net/~viric/soft/tm/
Author: Lluis Batlle i Rossell <viric_at_vicerveza_dot_homeunix_dot_net>
Terminal mixer can start processes inside a pseudo-terminal, which can
be accessed through a Unix socket, TCP or even raw ethernet (not yet
ported to FreeBSD). The programs can be linked to the current
terminal, or they can be unlinked like in nohup. But even in this
latter case you can connect to them using the mentioned protocols.
tm can also start programs as if they communicate through pipes
instead of terminals, and this can be quite useful for
remote-controlling applications.
More than one client can connect to the served pseudo-terminal, either
using tm as a client or telnet for TCP. You can choose if they are
only allowed to read, or they can also contribute on input.
WWW: http://vicerveza.homeunix.net/~viric/soft/tm/
Author: Lluis Batlle i Rossell <viric_at_vicerveza_dot_homeunix_dot_net>
2007-12-18 16:44:11 +01:00
|
|
|
COMMENT= Terminal mixer
|
|
|
|
|
|
|
|
|
|
PLIST_FILES= bin/${PORTNAME}
|
|
|
|
|
PORTDOCS= ChangeLog DOCS index.html
|
|
|
|
|
MAKE_ENV= LINUX_LIBS=-lutil
|
|
|
|
|
|
|
|
|
|
post-extract:
|
|
|
|
|
@${MV} ${WRKSRC}/web/index.html ${WRKSRC}/
|
|
|
|
|
|
|
|
|
|
post-patch:
|
|
|
|
|
@${REINPLACE_CMD} -e 's|$$^|$${.ALLSRC}|;/^GLIBCFLAGS/d;/^CFLAGS/d;\
|
|
|
|
|
/^CC/d;/^ifeq/,/^endif/d' ${WRKSRC}/Makefile
|
|
|
|
|
@${REINPLACE_CMD} -e 's|pty.h|libutil.h|' ${WRKSRC}/app_term.c
|
|
|
|
|
@${ECHO_CMD} '#include <string.h>' >> ${WRKSRC}/main.h
|
|
|
|
|
|
|
|
|
|
do-install:
|
|
|
|
|
@${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${PREFIX}/bin/
|
|
|
|
|
.ifndef NOPORTDOCS
|
|
|
|
|
@${INSTALL} -d ${DOCSDIR}/
|
|
|
|
|
@cd ${WRKSRC}/&&${INSTALL_DATA} ${PORTDOCS} ${DOCSDIR}/
|
|
|
|
|
.endif
|
|
|
|
|
|
|
|
|
|
.include <bsd.port.mk>
|
