On Saturday 02 June 2007 08:07:48 Marc G. Fournier wrote:
--On Saturday, June 02, 2007 05:28:31 +0000 "L. Rahyen"
I'm pretty sure he is. There is problems with FreeBSD that needs to be resolved by FreeBSD community - i.e. by people who knows FreeBSD and have time, will and neccessary skills to help. Problems will never resolve magically themself. Unfortunatelly most (all?) Wine developers know little > or nothing about FreeBSD and cannot solve these problems. And I know nothing about FreeBSD too - I even never used it... You may want to search for FreeBSD related bugs in bugzilla to understand current problems with Wine and FreeBSD better.
Well, it kind of works both ways ... one has to know what the problem if with wine under FreeBSD before one can provide a 'FreeBSD solution' to it :(
Right. And it's not as if we didn't try. Just two days ago, I've sent the following email to the freebsd-hackers mailing list: http://lists.freebsd.org/pipermail/freebsd-hackers/2007-May/020761.html
So far I've received one response, telling me to contact the ports maintainer. I haven't followed up on this yet, but being a maintainer for a couple of RPMs myself, I know that just being the maintainer doesn't mean I know how to fix the source code of the package I maintain. I was kind of hoping for some FreeBSD developers who know the memory management of their OS to at least offer some pointers on where to look. Didn't happen so far.
As I said in my email, I'm really happy to provide the Wine side of things for this bug, but I don't feel like doing the FreeBSD research. I don't use FreeBSD and my time is limited.
Cheers, Kai