On Jun 8, 2011, at 21:31, David Baumgold wrote:
>>> New port: iTerm2
>>
>> How does this relate to the iTerm port? (Does this conflict with it?)
>
> iTerm2 is a fork of the iTerm project. I have this port installing to
> ${applications_dir}/iTerm2.app, so it shouldn't conflict with iTerm.app.
On Wed, Jun 8, 2011 at 10:23 PM, Ryan Schmidt wrote:
> > New port: iTerm2
> How does this relate to the iTerm port? (Does this conflict with it?)
>
iTerm2 is a fork of the iTerm project. I have this port installing to
${applications_dir}/iTerm2.app, so it shouldn't conflict with iTerm.app.
> Wh
On Jun 8, 2011, at 01:19, Ryan Schmidt wrote:
> If that doesn't help, can you attach the config.log?
Scott informed me off-list that he worked around the issue by reinstalling
MacPorts from the tarball.
___
macports-dev mailing list
macports-dev@li
On Jun 8, 2011, at 20:43, singingwolf...@macports.org wrote:
> Revision: 79310
> http://trac.macports.org/changeset/79310
> Author: singingwolf...@macports.org
> Date: 2011-06-08 18:43:04 -0700 (Wed, 08 Jun 2011)
> Log Message:
> ---
> New port: iTerm2
How does this relate
On Jun 7, 2011, at 10:38 PM, Scott Cherf wrote:
> The following bug report could not be filed via the normal Trac interface
> because my email address, ch...@ambient-light.com, contains the text fragment
> 'Ambien', which is apparently verboten. If someone would be so kind as to
> file this for
