daemon_controller is a library for starting and stopping specific
daemons programmatically in a robust, race-condition-free manner.
It's not a daemon monitoring system like God or Monit. It's also not a
library for writing daemons.
It provides the following functionality:
Starting daemons. If the daemon fails to start then an exception
will be raised. daemon_controller can even detect failures that
occur after the daemon has already daemonized.
Starting daemons is done in a race-condition-free manner. If another
process using daemon_controller is trying to start the same daemon,
then daemon_controller will guarantee serialization.
daemon_controller also raises an exception if it detects that the
daemon is already started.
Connecting to a daemon, starting it if it's not already started.
This too is done in a race-condition-free manner. If the daemon
fails to start then an exception will be raised.
Stopping daemons.
Checking whether a daemon is running.
OK ajacoutot@
Ronn builds manuals. It converts simple, human readable textfiles to
roff for terminal display, and also to HTML for the web.
The source format includes all of Markdown but has a more rigid
structure and syntax extensions for features commonly found in manpages
(definition lists, link notation, etc.). The ronn-format(7) manual page
defines the format in detail.
OK sthen@
Inspired by ctemplate and et, Mustache is a framework-agnostic way to
render logic-free views.
As ctemplates says, "It emphasizes separating logic from presentation:
it is impossible to embed application logic in this template language."
OK sthen@
Jeweler provides the noble ruby developer with two primary features:
* a library for managing and releasing RubyGem projects
* a scaffold generator for starting new RubyGem projects
OK sthen@
ruby-git provides an object-oriented interface to git's command line
interface, allowing for both read and write operations on git
repositories.
OK sthen@
rspec 1 using rspec and rspec 2 using rspec2. Additionally, add
support for ruby and testrb, calling the appropriate binary for the
ruby implementation.
Start checking sanity of MODRUBY_REGRESS entry, using a fatal error
if it is defined and doesn't contain a recognized word.
Instead of RAKE_REGRESS_TARGET and RSPEC_REGRESS_TARGET, just use
MODRUBY_REGRESS_TARGET for all cases. On ruby 1.9, modifying the
environment to always look in the current directory for libraries
(the ruby 1.8 behavior), since many ports depend on that for regress.
Allow ports to set their own regress environment and current directory
using MODRUBY_REGRESS_ENV and MODRUBY_REGRESS_DIR.
Create /usr/ports/packages/i386/no-arch/p5-Devel-Symdump-2.07p1.tgz
Found newer package p5-Devel-Symdump-2.0601 in /usr/ports/plist/i386
Found newer package p5-Devel-Symdump-2.0604 in /usr/ports/plist/i386
but version 2 has 4 packages (core, expectations, mocks, and rspec).
Stick version 1 in a subdir named 1, and the version 2 packages
each in their own subdir.
Upgrade version 1 to 1.3.2, the latest version, as some ports depend
on >=1.3.0,<2.0. Because rubygems does not correctly handle the
case where two versions of the same library install different
binaries, manually hack the version 1 spec binary to work.
Both version 1 and version 2 ship with the autospec binary, so comment
it out from version 1 so the versions don't conflict.
This requires changes to dependent ports, which will be committed
shortly.
- get rid of libtool and thus rpath bugs
- install libexec files as they're also needed
- copy the crt files in lib/gcc/i386-mingw32/3.4.5 as the
compiler looks for them in there and not in lib
- disable shared and thus lose the platform specific files
(noticed by jeremy@ as well)
- adapt the README after these changes
Rocrail can control a model train layout from one or more computers. You
can run trains directly from your computer, and you can have the
computer run trains automatically for you. You can even have some of the
trains on your layout running automatically while you control others by
hand. Rocrail is two programs; the Rocrail Server and the Rocview
Client. These programs work with each other using Internet protocols,
and do not need to be on the same computer. You can use Rocrail from a
single computer connected directly to your layout, and you can also
control your layout from any computer on your home network, or over the
Internet. Rocrail also has a web interface, which will let you run the
layout from a web browser.
OK sthen@
