Scott Long wrote:
Having it as a loadable module that is essentially private to PC-BSD
(though open source, of course) will lead to questions of why Wine works
in PC-BSD and not FreeBSD. That's fine if your intention is to create
a fork of FreeBSD, but I don't know if that's what you really want.
There is no need for it to be private - we can just easily have it in
the same port or in separate port (wine_kmod?) and get wine RUN_DEPEND
on it.
We have been using this scheme with VmWare for ages now and everybody
seems to be happy. Indeed, as Robert has pointed out, wine is special in
its needs to access some kernel internals to emulate sufficiently
different threading model. Those internals are not and probably will
never be exposed via POSIX layer, so that loadable module approach makes
lot of sense.
-Maxim
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
