Hi Jochen,
The .app seems to require Growl, however, which port cannot fetch
It seems that growl.info currently has tarballs of the source only as far back as 0.7.4, and 0.7 is now only available via Subversion, so this port clearly has to be updated (though you probably realised that). I'm not able to do it just now, but if I get it working and am confident that I've done so correctly, I'll pick up maintenance.
By the way, are the plans for an mrxvt port?
There might be now that you mention it :-) Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms@macports.org
boeyms@macports.org on Saturday, April 14, 2007 at 8:12 AM -0800 wrote:
It seems that growl.info currently has tarballs of the source only as far back as 0.7.4, and 0.7 is now only available via Subversion, so this port clearly has to be updated
There is a 0.7.6 tarball: http://growl.info/downloads_developers.php But the Growl port has been broken for awhile. There have been some attempts to fix it, but it seems that beuliding from source is problematic. http://trac.macosforge.org/projects/macports/ticket/4996 If it can be fixed easily that's be great, but if the developers don't support building from source versy well I wonder if this isn't just one of those apps that are better off installed as a binary. If so, and I don't know if that's true or not, it should be deleted from MacPorts. Mark
On 4/14/07, markd@macports.org <markd@macports.org> wrote:
If it can be fixed easily that's be great, but if the developers don't support building from source versy well I wonder if this isn't just one of those apps that are better off installed as a binary. If so, and I don't know if that's true or not, it should be deleted from MacPorts.
I was just thinking something similar. What would be the benefit of compiling iTerm from scratch when it comes as a Universal binary on a DMG? (That's a serious question...since I only use MacPorts for command line things) Patrick
On 15.04.2007, at 02:26, Patrick Burleson wrote:
What would be the benefit of compiling iTerm from scratch when it comes as a Universal binary on a DMG? (That's a serious question...since I only use MacPorts for command line things)
I can answer one part of that: what is the benefit of having iTerm as part of MacPorts instead of just downloading it from the web? Well, for one it's easier to get. I heard these great stories about iTerm from my colleague, went to my Mac, typed sudo port install iTerm voila, there it comes. Moreover I automatically get new versions when I do sudo port upgrade active because some of the nice guys at MacPorts updates the package once in a while;) This approach also prevents clutter of my Application folder, because typically I forget to remove Apps I don't use anymore, so they only eat up hd-space. With MacPorts I have a single point to look for, also in that respect. Can we just put a dmg into a port and install from that? There someone of the MacPorts developers has to answer... Greetings, Jochen -- Fritz-Haber-Institut der MPG -- Department of Molecular Physics Faradayweg 4-6 (C1.03) D-14195 Berlin, Germany phone: +49-30-84135686 fax: +49-30-84135892
On Apr 15, 2007, at 10:06 AM, Jochen Küpper wrote:
On 15.04.2007, at 02:26, Patrick Burleson wrote:
[..] Moreover I automatically get new versions when I do sudo port upgrade active because some of the nice guys at MacPorts updates the package once in a while;)
iTerm's 'port' is currently at 0.8.2 although 0.9.5 is out. Furthermore I believe iTerm has a builtin auto-update feature which obsoletes upgrading through MacPorts (or even interferes with it) Regards, Elias Pipping
On Apr 15, 2007, at 03:43, Elias Pipping wrote:
On Apr 15, 2007, at 10:06 AM, Jochen Küpper wrote:
On 15.04.2007, at 02:26, Patrick Burleson wrote:
[..] Moreover I automatically get new versions when I do sudo port upgrade active because some of the nice guys at MacPorts updates the package once in a while;)
iTerm's 'port' is currently at 0.8.2 although 0.9.5 is out. Furthermore I believe iTerm has a builtin auto-update feature which obsoletes upgrading through MacPorts (or even interferes with it)
Right. That's a reason why the CyberDuck port was removed, for example. And it's a reason why Growl should be removed, since it also has an auto-update feature.
Growl is a potential dependency[1] of other ports in the ports tree. The mere fact that it has an auto-update feature is not reason to remove it from the ports tree. Another comment, that we should remove it since the developers do not seem to support building it yourself, is slightly incorrect: because Growl uses AppleScript, it does not like building from the command line. This is (obviously) a problem for us, but I think it is more of an Apple problem than a Growl problem. Also, since we are wishing to eventually be able to distribute binaries instead of requiring that users install Xcode, repackaging binaries should not be a problem for us, particularly if we are able to get our act together and not let ports get too stale. [1] potential dependency = we would be depending on it if it could build reliably from the command line On 15 Apr 2007, at 05:47, Ryan Schmidt wrote:
On Apr 15, 2007, at 03:43, Elias Pipping wrote:
On Apr 15, 2007, at 10:06 AM, Jochen Küpper wrote:
On 15.04.2007, at 02:26, Patrick Burleson wrote:
[..] Moreover I automatically get new versions when I do sudo port upgrade active because some of the nice guys at MacPorts updates the package once in a while;)
iTerm's 'port' is currently at 0.8.2 although 0.9.5 is out. Furthermore I believe iTerm has a builtin auto-update feature which obsoletes upgrading through MacPorts (or even interferes with it)
Right. That's a reason why the CyberDuck port was removed, for example. And it's a reason why Growl should be removed, since it also has an auto-update feature.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
Randall Wood says:
because Growl uses AppleScript, it does not like building from the command line.
I just got the recentmost growl from one of the links in this thread, and didn't see any obvious README/INSTALL with installation instructions in it -- but there's a ./build.sh which I ran and it did everything with SUCCESS apparently. What and where do I deploy now and how do I install iTerm given I did obtain growl manually? Cheers, Alexy
participants (8)
-
Alexy Khrabrov
-
Boey Maun Suang
-
Elias Pipping
-
Jochen Küpper
-
markd＠macports.org
-
Patrick Burleson
-
Randall Wood
-
Ryan Schmidt