[MacPorts] #14905: metacity fails to build (core/compositor.c
issues)
MacPorts
trac at macosforge.org
Thu May 1 02:13:43 PDT 2008
#14905: metacity fails to build (core/compositor.c issues)
----------------------------------+-----------------------------------------
Reporter: paulbeard at gmail.com | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: new
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.6.0
Resolution: | Keywords: metacity
----------------------------------+-----------------------------------------
Comment (by rhwood at macports.org):
Replying to [comment:22 paulbeard at gmail.com]:
> I was under the impression it was possible to use a different WM.
One can ''use'' a different WM, but one still needs metacity to build in
my experience. GNOME clings to metacity as a lowest common denominator and
is designed so that the failure of a different WM to start (for example
code in the WM to handle complex effects bomb out on bad X drivers) will
lead to metacity starting to provide a minimally acceptable user interface
(at least this is my experience in Fedora8/RHEL5 land).
As far as I can recall, the gnome-control-center builds metacity-specific
stuff as well.
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14905#comment:24>
MacPorts </projects/macports>
Ports system for Mac OS
More information about the macports-tickets
mailing list