LPRng has been left off unmaintained in the ports tree for its last 14
releases and is mostly dead; there are alternatives.
no objection from my fellow porters
version of mcollective.
Force ruby 1.8; version 1.9 is not functionnal yet.
Simplify patching the config files by using a regex.
Use BSD_INSTALL_*
Use $RUBY in the rc script.
Take maintainer.
More work to come, so still not hooked to the build.
The "wm" stands for webmachine. This OTP application contains the core
of the erchef REST API implemented on top of the Webmachine toolkit. The
URL routing that matches URLs with Erlang modules handling requests for
those URLs is defined in `priv/dispatch.conf`.
ok aja@
rebar wants to download missing dependencies on the fly, but that won't work out
too good in the ports tree, so erlang.port.mk now removes those dependency declaration
sections.
Implement a restart command for the service provider and use '-f' as well.
No need to specify a 'stop' common, our rc.d(8) is generic enough.
ok robert@ (maintainer)
* move the current port to ruby-puppet/3
* add a new puppet-2.7.X port under ruby-puppet/2
This allows us to ship with 2 different versions of Puppet. Since the
Enterprise version is still running 2.7, we want to have a matching
client because running puppet3 against a puppet2 server is highly
discouraged and will mostly no work correctly.
ok jasper@, robert@ (maintainer)
The stats_hero application can help you instrument your Erlang
application with metrics that will be reported to estatsd and browsable
in Graphite.
ok aja@
Lager is a logging framework for Erlang. Its purpose is to provide a
more traditional way to perform logging in an erlang application that
plays nicely with traditional UNIX logging tools like logrotate and
syslog.
ok aja@
