Growl: Update to latest version

[ryan@…]

Please update Growl from 1.1.4 -> 1.2.1.

Keep in mind the new version requires 10.5.

[nerdling (Jeremy Lavergne)]

I'd dropping 10.4 support, or the less ideal creating a second growl port (growl11). Also, we're in maintainer timeout territory.

[nerdling (Jeremy Lavergne)]

I attached a diff of my update. Unfortunately, there's a code signing section involved.

=== BUILD NATIVE TARGET GrowlHelperApp OF PROJECT Growl WITH CONFIGURATION Release ===
Check dependencies
Code Signing Identity 'Growl code-signing certificate' does not match any valid, non-expired, code-signing certificate in your keychain.
[BEROR]Code Signing Identity 'Growl code-signing certificate' does not match any valid, non-expired, code-signing certificate in your keychain.
** BUILD FAILED **

If anyone's bored and wants to find if there's a build option to disable this, it's all that's standing in the way.

[jmroot (Joshua Root)]

We should probably only install the framework. The helper and prefpane are not needed for dependents to build, and are likely to be installed outside of MacPorts.

[boeyms@…]

Reassigning to macports-tickets@… as I have relinquished ownership of this port.

[ryandesign (Ryan Carsten Schmidt)]

Duplicate #31849 requests updating to 1.3.0 and provides ​this link with instructions. However, the instructions begin by stating that Lion is required to build the latest version from source, so that's probably not a good idea to impose on MacPorts users at this time, since we still have users using Snow Leopard, Leopard, and Tiger.

[nerdling (Jeremy Lavergne)]

Can we put the version and checksum lines inside of a platform block, and any other needed components? That could let each OS version run it's current version without having to create a separate port (e.g. growl/growl11/growl12).

[ryandesign (Ryan Carsten Schmidt)]

We have done that in other ports, like ld64. Previously, it has been considered bad practice, because the PortIndex file is shared among all OS versions, and only the version that's seen by the machine generating the PortIndex (which currently runs Snow Leopard) would show up in the output of "port info", "port search", etc.

[neverpanic (Clemens Lang)]

Patch against an empty directory for a growl13 port

[neverpanic (Clemens Lang)]

I've attached a patch against an empty directory generating a Portfile and set of patch files that will build Growl 1.3. I'm not entirely sure, but I think this builds the same stuff in build and destroot phase; maybe somebody with more experience in using Xcode and xcodebuild can shed some light on how to avoid this.

[ryandesign (Ryan Carsten Schmidt)]

You know, a lot of xcode portgroup ports do that... I never understood why.

[ecronin (Eric Cronin)]

I had to edit port1.0/portfetch.tcl to quote $hg.tag when constructing the hg command line in order to successfully clone the source... Did you not have to do that? My tcl skills are weak, I couldn't find a proper escaping of the value in the Portfile itself that would have turned into --rev "Growl.app 1.3.3" or --rev Growl.app\ 1.3.3 when passed to system()...

[neverpanic (Clemens Lang)]

Oh, yeah, forgot to mention that. I haven't found a way to quote correctly without editing base, either. This change should probably go into base.

[neverpanic (Clemens Lang)]

Added the necessary quotes in r95438.

[cooljeanius (Eric Gallager)]

Cc Me!

[cooljeanius (Eric Gallager)]

Replying to jmr@…:

We should probably only install the framework. The helper and prefpane are not needed for dependents to build, and are likely to be installed outside of MacPorts.

+1 for this. I just re-installed the Growl port and it overwrote the prefpane that I had installed separately.

[jmroot (Joshua Root)]

Replying to egall@…:

Replying to jmr@…:

We should probably only install the framework. The helper and prefpane are not needed for dependents to build, and are likely to be installed outside of MacPorts.

+1 for this. I just re-installed the Growl port and it overwrote the prefpane that I had installed separately.

Well, now that you have to pay for the official binary, it's worth having a subport for the other bits too, which nothing would depend on.

[mojca (Mojca Miklavec)]

Cc Me!

[mf2k (Frank Schima)]

I did not mean to assign this to myself.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #49673.

[raimue (Rainer Müller)]

Since there was no significant progress for over 3 years now, I would simply suggest to remove the outdated Growl @1.1.6_1 port. Providing such an outdated version is not helpful. If someone comes up with a current Portfile it can be re-added later.

Any objections to removal of ports growl, py-growl, and p5-net-growl?

[nerdling (Jeremy Lavergne)]

I second it; default to action and remove it please.

[mike-savory]

Yes, remove. Long since dropped from my radar.

[mojca (Mojca Miklavec)]

Can someone quickly recap the situation and correct me?

• This used to be one of the best notification systems.
• After version 1.2.2 it became a payed software on app store, with the latest version 2.1.3 released on 29th October 2013 being sold for $3.99 on App Store.
• One can fetch the sources for the same software on ​Google Code (latest tag 2.1.2, latest commit on 12th Oct, 2013), compile them and get the same functionality as with payed version(?)
• The sources need at least 10.7 to be compiled (which wouldn't be acceptable years ago, but might be acceptable now). No clue whether the software still compiles & works on 10.10 and later.
• The development stopped completely in October without any official notice about the end of development. There were a number of attempts to attract more users by offering some ​discounts, but the last post was in December 2013.
• In January 2016 the sources will be removed from Google Code (as Google code is shutting down) and vanish in Ethernity.
• (Growl for Windows has been "rescued" and transferred to GitHub, even though there doesn't seem to be happening much either.)
• The introduction of System Notifications & the fact that Growl became a payed application (at almost the same time) meant pretty much "the end" of the app.
• Despite that a number of apps still support Growl, so it's not entirely obsolete yet.

Can someone please correct my guesses?

[ryandesign (Ryan Carsten Schmidt)]

I'll just say that I still use Growl 1.2.2 (installed outside of MacPorts) successfully on El Capitan.

[mojca (Mojca Miklavec)]

Thanks for confirmation that it still works. I also still have a standalone Growl 1.2.2 installed on 10.7 (mostly because I'm too lazy to take two days for doing a complete wipe-out of the disk and install a new OS from scratch) and have never tried the version that comes with MacPorts. The only annoying thing is that the version 1.2.2 constantly keeps bugging me about an upgrade.

I have no clue whether a packaged version 2.1.2/2.1.3 would be helpful to users and how much benefit that version brings compared to System Notifications.

I don't oppose removing version 1.1.x. I'm only asking whether we should try to package 2.1.x.

[ryandesign (Ryan Carsten Schmidt)]

You can open the preference pane and disable checking for updates.

[raimue (Rainer Müller)]

In bf25ee27d67c2f646f1865559a3a01243c75a3ef/macports-ports:

Growl: Remove outdated and abandoned ports

Ports are outdated for years, last changes from 2010. Attempts to update
the port to a recent version were not successful. Later versions are
commercial and can be purchased in the Mac App Store.

Closes: #32911
Closes: #22684
Closes: #14273