mxcl/homebrew — Issue #8680: Growl and homebrew
Author: ColinHebert
Created: 2011-11-19 14:16:36+00:00
State: open

Hello,

I'm currently working on Growl integration in homebrew (#8649) and I have a few questions.

First, I looked at the current packages related to growl, there is three of them :
````growlnotify````, a tool used to create growl notification from the command line. Here, it's a binary file copied in /bin (which is downloadable from [growl.info](http://growl.info/downloads)) instead of the source files (available on the growl repository).
````growly````, a tool used to create growl notifications from another command result, in command line. Depends on growly and actually one-page bash script used as a wrapper for growlnotify.
````growlme````, a tool used to create growl notifications from another command result, in command line. This time it doesn't depends on growly but it's still a one-page script (in python).

I have strictly nothing personal against these packages, but do they have their place in homebrew ?

On the other hand, I was considering to add ````HardwareGrowler```` which is an official extra for growl, only available from app store ($2~) but still open-source.

So here is the thing, for ````HardwareGrowler````, should I create a formula, or should I just add a new option the the current growl formula (#8649) ?
Regarding ````growlnotify````, I agree that it's easier to install it from brew but in this case, downloading the actual source code and compiling it would be better. Should I update the growlnotify formula to do so ? Or should I add another option to the growl formula to install at the same time growlnotify (which is worthless without growl). Or should it be simply removed ?

Regarding ````growly```` and ````growlme````, should they stay there ? Note that growly depends on growlnotify, so if it has to stay, growlnotify has to stay on a separated formula.