On 2015/03/24 14:39, Kent R. Spillner wrote:
> With attachment this time.
>
> On Tue, Mar 24, 2015 at 02:35:53PM -0500, Kent R. Spillner wrote:
> > Attached is an updated version based on feedback from czarkoff@:
> >
> > - Reword DESCR
> > - Prefer ${...} over $(...)
> >
> > Ok?
> >
> > On Mon, Mar 23, 2015 at 11:57:54AM -0500, Kent R. Spillner wrote:
> > > Ping.
> > >
> > > On Wed, Mar 18, 2015 at 12:27:06PM -0500, Kent R. Spillner wrote:
> > > > Attached is a new port for websocketd, which lets you access any command
> > > > line tool via a websocket. It depends on the go-websocket port sent
> > > > previously.
> > > >
> > > > $ cat pkg/DESCR
> > > > websocketd is a small command-line tool that will wrap an existing
> > > > command-line interface program, and allow it to be accessed via a
> > > > WebSocket.
> > > >
> > > > WebSocket-capable applications can now be built very easily. As long as
> > > > you can write an executable program that reads `STDIN` and writes to
> > > > `STDOUT`, you can build a WebSocket server. Do it in Python, Ruby, Perl,
> > > > Bash, .NET, C, Go, PHP, Java, Clojure, Scala, Groovy, Expect, Awk,
> > > > VBScript, Haskell, Lua, R, whatever! No networking libraries necessary.
> >
> >
common style is to split BUILD_DEPENDS onto multiple lines, e.g.
-BUILD_DEPENDS = lang/go www/go-websocket
+BUILD_DEPENDS = lang/go \
+ www/go-websocket
I'm wondering about CATEGORIES though. net seems like maybe it's more
appropriate than www? (actually...perhaps net is a better place for
go-websocket too, perhaps with www as a secondary category?...)
