On Wed, Jun 8, 2011 at 10:23 PM, Ryan Schmidt <ryandes...@macports.org>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.
> Why not just update the iTerm port to version 2?
>
Because a fork is not the same as an update. Also, the project seems to be
going by the name "iTerm2", rather than "iTerm, version 2".
> Does this close https://trac.macports.org/ticket/27787 ?
> What about https://trac.macports.org/ticket/20377 ?
>
I hadn't seen those tickets before. This should definitely close 27787,
since that ticket is simply requesting that iTerm2 be packaged in MacPorts
-- and now it is. I don't think it closes 20377, since that ticket is
addressing build failures in the iTerm port. If/when the iTerm project
announces that its users should switch to iTerm2 instead, then we
can obsolete the iTerm port, but as it is, I know there are people still
using iTerm, and who might not be happy with MacPorts upgrading them to an
unstable fork of the project.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
