According to Giuseppe Pagnoni <[email protected]> on Mon, 10/11/10 at 10:57: > > thank you very much for your reply, it does seem to be the same type > of bug. However, and I apologize for being dense here, it is not > immediate to me how to proceed practically to apply the patch from > within the ports framework. Also, I still wonder why the patch hasn't > been incorporated in the tree given that the bug is known....
I am not able to answer your final question - that is left to the ports maintainers to address. I simply installed the latest (was it 1.7.5) xorg-server at that time and added those half dozen patches. If 1.7.7 solved the problem, then I'm not sure what issue(s) you have. If you want to have FreeBSD ports upgraded, I would contact the port's maintainers directly. I chose not to install xorg-server 1.7.7 since I was unsure if there were other dependencies or issues that might arise from doing so. I'm not used to "patch"ing a mature, released port, so for me even that was a leap of faith! :-) Just for clarity, I did not formally "patch" this port (xorg-server). I went into the directory tree beneath the "work" directory, found the dit/events.c file, and made those above mentioned (about six or so) small source code patches. I then re-made the port and re-installed the port. After it tested successfully, I reported my results to the -questions list in case it would help others. YMMV. And good luck! Regards, web... -- William Bulley Email: [email protected] 72 characters width template ----------------------------------------->| _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
