[MacPorts] #17453: Clarify policy of duplicating ${x11prefix}

[MacPorts]

#17453: Clarify policy of duplicating ${x11prefix}
-----------------------------------+----------------------------------------
 Reporter:  mcalhoun@…             |       Owner:  jeremyhu@…           
     Type:  defect                 |      Status:  assigned             
 Priority:  Normal                 |   Milestone:  Port Bugs            
Component:  ports                  |     Version:  1.6.0                
 Keywords:                         |        Port:                       
-----------------------------------+----------------------------------------

Comment(by mcalhoun@…):

 Replying to [comment:5 ryandesign@…]:
 > The reason for our policy of using MacPorts versions instead of Apple
 versions is so that we can keep it up to date. Or can you guarantee a
 change in Apple policy, that Apple will always keep its libraries up to
 date from now on?
 I see your point, but it seems to me that we do rely on Apple software
 even though Apple makes no guarantees about how recent it is.[[BR]]
 X11 and gcc being the big ones.[[BR]]
 It seems that some ports are so closely tied to X11 that it is not a good
 idea to try to separate them out.[[BR]]
 Perhaps xrender and fontconfig are such ports.

 >
 > What is the matter with the MacPorts freetype configuration file? In any
 case, this discussion is not relevant in this ticket, so please either
 file a new one, or bring it up on the mailing list.
 There was some confusion on my part as to what the X11 policy should be,
 which is why I opened the ticket.[[BR]]
 It seemed like a good forum to hash some of these issues out.[[BR]]
 If others think that the mailing list is better, then that is fine.

-- 
Ticket URL: <http://trac.macports.org/ticket/17453#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS