[MacPorts] #13493: xorg-renderproto and render conflict
MacPorts
noreply at macports.org
Wed Nov 12 21:01:28 PST 2008
#13493: xorg-renderproto and render conflict
---------------------------------------+------------------------------------
Reporter: mww at macports.org | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: reopened
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.5.2
Resolution: | Keywords: render xorg-renderproto xorg
Port: xorg-renderproto, render |
---------------------------------------+------------------------------------
Comment(by ryandesign at macports.org):
Replying to [comment:22 mcalhoun@…]:
> Please forgive my ignorance, but why do some ports (such as gtk2) depend
on both xrender and xorg-renderproto?[[BR]]
> Shouldn't they simply depend on xrender and let xrender worry about
render vs xorg-renderproto?
Sounds sensible to me. Anybody see anything wrong with that? I would
remove render and xorg-renderproto as dependencies from all ports on
[comment:5 jmr's list above], except xrender, which should keep both until
a time in the future when we can assume everyone has upgraded, and also
until after everyone has upgraded to MacPorts 1.7.0 which has the fix that
properly removes removed dependencies from the receipts or wherever it's
stored...
--
Ticket URL: <http://trac.macports.org/ticket/13493#comment:23>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list