quartz/x11 conflict

Jamie Paul Griffin jamie at kode5.net
Mon Aug 20 06:45:18 PDT 2012

== Tabitha McNerney wrote on Mon 20.Aug'12 at  1:00:59 -0500 ==

> On Sat, Aug 18, 2012 at 6:31 PM, Brandon Allbery <allbery.b at gmail.com>wrote:
> > On Sat, Aug 18, 2012 at 7:16 PM, Tabitha McNerney <tabithamc at gmail.com>wrote:
> >
> >> 3.) After creating this new instance of Mountain Lion, I was bewildered
> >> when I saw in the Launchpad an X11 icon. I double clicked the X11 icon and
> >> an alert panel asked me if I wanted to install it (I decided not to because
> >> I wanted to understand why X11 as an install option was
> >>
> >
> > I am under the impression there is a dummy that installs XQuartz when
> > invoked, to make life easier for people expecting X11.app to be there.
> >  Likewise the binaries under /usr/X11 advise the user to install XQuartz if
> > invoked.
> >
> > In short, Apple is no longer preinstalling an out-of-date XQuartz, but
> > just referring people to the real thing.
> >
> Thanks for the update on how Apple is handling X11, this makes sense that a
> lot of people might be expecting X11 so its essentially a placeholder that
> links to XQuartz (I'll have to try it out the next time I'm booted into
> Mountain Lion).

It's interesting reading posts like this and learning about others' experiences with upgrading OS X. I have to say, the changes they make like the one discussed in this thread I find a little worrying. I wonder about the direction they're taking the OS X platform. I mean I like it purely because of its UNIX subsystem. iOS, etc, completely takes that away from the user so I hope that won't happen with OS X releases in the future. 

More information about the macports-users mailing list