|

»

»

MacPorts - Developer

+system_x11 to bite the dust

View: Old framed views

11 Messages — Rating Filter: Alert me

Jeremy Huddleston-5 +system_x11 to bite the dust - So, the MacPorts-provided X11 libs should be regression free over what is installed in any x11prefix. The... Loading...

‹

Marcus Calhoun-Lopez-2 Jeremy Huddleston <jeremyhu@...> writes: > > So, the MacPorts-provided X11 libs should be regression free over what... Loading...

‹

Jeremy Huddleston-5 On Apr 29, 2009, at 13:57, Marcus Calhoun-Lopez wrote: > Isn't there a case to be made for hedging our bets? > > I... Loading...

‹

Marcus Calhoun-Lopez-2 Jeremy Huddleston <jeremyhu@...> writes: > > You bring up a good point, but I don't think it's as big a concern as ... Loading...

‹

Anders F Björklund-2 Jeremy Huddleston wrote: > Can we successfully nuke the backwards-compatible system_x11 > variant now? If any... Loading...

‹

Jeremy Huddleston-5 On Apr 29, 2009, at 12:43, Anders F Björklund wrote: > >> After this is done, I'm going to go through and start... Loading...

‹

Anders F Björklund-2 Jeremy Huddleston wrote: >> I think ${x11prefix} was mostly to avoid hardcoding /usr/X11R6 >> (or /usr/X11), but I... Loading...

‹

David Evans-14 Jeremy Huddleston wrote: > So, the MacPorts-provided X11 libs should be regression free over what > is installed in... Loading...

‹

Jeremy Huddleston-5 On Apr 29, 2009, at 12:41, David Evans wrote: > I agree that this would be a move toward simplification, but the >... Loading...

‹

David Evans-14 Jeremy Huddleston wrote: > > On Apr 29, 2009, at 12:41, David Evans wrote: >> I agree that this would be a move... Loading...

‹

Ryan Schmidt-24 On Apr 29, 2009, at 14:24, Jeremy Huddleston wrote: > So, the MacPorts-provided X11 libs should be regression free... Loading...