New port: Marionette Collective

[matt@…]

Please find attached a Portfile for the Marionette Collective aka MCollective.

The only nit I found was that I needed to change the hashbang at the top of the Ruby script installed as a daemon from "#!/usr/bin/env ruby" to "#!${ruby.bin}" otherwise it couldn't find the support libraries when installed with "port load ...". This only happened when running under launchd, I could manually start it up so I'm not sure how best to fix it.

[matt@…]

Portfile for Marionette Collective

[drkp (Dan Ports)]

Replying to matt@…:

The only nit I found was that I needed to change the hashbang at the top of the Ruby script installed as a daemon from "#!/usr/bin/env ruby" to "#!${ruby.bin}" otherwise it couldn't find the support libraries when installed with "port load ...". This only happened when running under launchd, I could manually start it up so I'm not sure how best to fix it.

This makes sense; env ruby launches whatever ruby binary is in your $PATH, and launchd is probably using an empty path. It's a good practice to change this to the absolute path anyway -- there could be a different ruby installation in the user's path, and we want to be sure we're using the one we installed rb-stomp for.

[drkp (Dan Ports)]

When installing configuration files that the user is supposed to edit, we need to make sure they're not overwritten on update, as explained in wiki:PortfileRecipes#configfiles

It sounds like server.cfg and client.cfg, and maybe facts.yaml? What about rpc-help.erb?