Commit Graph

8 Commits

Author SHA1 Message Date
Vanilla I. Shu
f9611b2a9e Support STAGEDIR. 2013-11-16 13:25:19 +00:00
Baptiste Daroussin
83f65384c9 Add NO_STAGE all over the place in preparation for the staging support (cat: sysutils) 2013-09-20 23:05:58 +00:00
Boris Samorodov
2176d86e13 . add LICENSE=GPLv2;
. bump PORTREVISION;
. NOPORTDOCS -> PORT_OPTIONS:MDOCS;
. trim Makefile headers.
2013-06-14 16:26:47 +00:00
Doug Barton
989772c9ac The vast majority of pkg-descr files had the following format when they
had both lines:

Author: ...
WWW: ....

So standardize on that, and move them to the end of the file when necessary.

Also fix some more whitespace, and remove more "signature tags" of varying
forms, like -- name, etc.

s/AUTHOR/Author/

A few other various formatting issues
2011-10-24 09:11:38 +00:00
Martin Wilke
a9481afc8a - Get Rid MD5 support 2011-03-19 12:38:54 +00:00
Mark Linimon
d72c560b21 Reset infofarmer due to maintainer-timeouts and no response to email.
Hat:	portmgr
2008-09-07 00:19:05 +00:00
Andrew Pantyukhin
c5728c14a9 - Update to 0.4.1 2008-05-03 19:06:02 +00:00
Andrew Pantyukhin
b94d3337c0 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 15:44:11 +00:00