Commits

Perry Metzger  committed ae8ac9e

update README

  • Participants
  • Parent commits bcb5c38

Comments (0)

Files changed (1)

+WHAT IS THIS?
+
 This branch represents an unofficial patched version of the Growl
-1.2.x sources taken from the last available public source tree. (It
-was forked from the maintenance-1.2 branch. The "default" branch seems
-to be old and crusty.)
+1.2.x sources taken from the last available public source tree.
 
-It builds cleanly under XCode 4.1 -- as set up, it constructs binaries
-that run only under Mac OS X 10.7 "Lion".
+(The tip of this tree is the "fork-1.2" branch, which was branched
+from the "maintenance-1.2" branch. The "default" branch seems to be
+old and unused.)
 
-It also incorporates a patch for HardwareGrowler.app, which otherwise
-crashes on Lion if your WiFi adapter changes state.
+This branch builds cleanly under XCode 4.1. As provided, it constructs
+binaries that run only under Mac OS X 10.7 "Lion", though people
+running Snow Leopard are probably better off using the official 1.2.x
+binaries anyway.
+
+This branch also incorporates a patch for HardwareGrowler.app, which
+otherwise crashes on Lion if your WiFi adapter changes state.
 
 None of this work is official, it is not endorsed by the growl.info
 folks, it is not guaranteed to work at all.
 
 HOW TO BUILD:
 
-0) You need XCode 4.1 installed
+0) You need to have XCode 4.1 installed
 1) Clone the repository.
 2) type "./build.sh" in the top directory. Better yet, do
    "./build.sh >/tmp/log 2>&1" and make sure when it is done that
    /tmp/log contains no "BUILD FAILED" lines.
-3) A zip file of the growl preferences will be in
+3) A zip file of the growl preferences will be left in
      build/Release/Growl.prefPane.zip
    To install it by hand (yes, this is cheesy)....
      a) Make sure you have no other version of growl (like 1.3 or 1.2.2)
    ALL -- HardwareGrowler seems to work, GrowlTunes seems to work, I
    haven't tested the others AT ALL.
 
-Patches to automate creating a release are of course welcome -- there
-is some existing release automation there but it doesn't seem to be
-"press one button" automatic, which it could be. (If I end up doing
-this too often I'll do that, or more likely, I'll just wait until
-someone else gets frustrated and does it.)
+Patches to automate creating a real release welcome -- there is some
+existing release automation there but it doesn't seem to be "press one
+button" automatic, which it could be. (If I end up doing this too
+often I'll do that, or more likely, I'll just wait until someone else
+gets frustrated and does it.)
+
+WHY DID I FORK THIS?
+
+I forked the Growl sources largely because Growl 1.3, available only
+on the Mac App Store, seemed to fail very badly for most of the people
+who installed it (including me), and the growl developers seemed
+fairly unsympathetic to people's complaints, claiming that there was
+no way they could have known of the various installer bugs it has, and
+that the failure of applications using old frameworks to talk to the
+new growl is the fault of the app developers. The 1.3 distribution
+also lacks working versions of the various "extras" that were in the
+past distributed with Growl.
+
+I think the developers should have withdrawn 1.3 until the problems
+were fixed, but they felt otherwise.
+
+Unfortunately, the Growl 1.3 sources are not currently available to
+the public, so it is not possible for me to simply fix those sources
+for myself and submit patches back to the developers.
+
+I would simply have continued using Growl 1.2.2, but the old
+HardwareGrowler was failing pretty badly for me under Lion, and I both
+wanted that fixed and to know that, if I needed to continue supporting
+Growl just for myself, that I could.
+
+Hopefully the Growl 1.3 branch from the official Growl maintainers
+will eventually become open source again and get straightened out so
+that it works for most users, but if it doesn't, a fork of the project
+will be able to provide a working Growl to Mac users.