Le 07-04-03 à 12:46, Mark Duling a écrit :
macports-dev@lists.macosforge.org on Tuesday, April 3, 2007 at 9:30 AM -0800 wrote:
Revision [ http://trac.macosforge.org/projects/macports/changeset/23516 ]23516 Author yves@macports.org Date 2007-04-03 09:30:46 -0700 (Tue, 03 Apr 2007)
Log Message
Make a more complete check : for Apple X11 with or without X11SDK (ticket:6188) for Apple X11SDK without X11 (ticket:10238) Also good for ticket:1551
Great. Can any of the other three related to XFree be closed?
This one is about Xorg. Xorg 7.2 supports GNU Hurd and Windows but still not darwin ... I wonder if we should not dump it altogether. Maybe do the same for Xfree86_44 ?
Don't know, I haven't tried. But it looks like a very weird idea to me. I mean, what can it give except loads of problems ? But I'm still young and naive ...
Closed. I did not think it was still open, never was a good idea anyway. Thanks yves
On Apr 3, 2007, at 12:27, Yves de Champlain wrote:
Don't know, I haven't tried. But it looks like a very weird idea to me. I mean, what can it give except loads of problems ? But I'm still young and naive ...
The bug says: "I tried to install XFree86 on MacOS 10.3 I have Apple's X11 (including development files) installed." As far as I can see, the user has just identified his problem right there. As far as I have been aware, you can either have XFree86 or Apple's X11 but not both because they go in the same place. I would close the bug as invalid, unless my understanding of this situation is wrong...
Le 07-04-03 à 16:58, Ryan Schmidt a écrit :
On Apr 3, 2007, at 12:27, Yves de Champlain wrote:
Don't know, I haven't tried. But it looks like a very weird idea to me. I mean, what can it give except loads of problems ? But I'm still young and naive ...
The bug says:
"I tried to install XFree86 on MacOS 10.3 I have Apple's X11 (including development files) installed."
As far as I can see, the user has just identified his problem right there. As far as I have been aware, you can either have XFree86 or Apple's X11 but not both because they go in the same place. I would close the bug as invalid, unless my understanding of this situation is wrong...
This would be a duplicate. What is particular here is "setting x11prefix" that don't work. But is it even supposed to ? yves
participants (2)
-
Ryan Schmidt
-
Yves de Champlain