Re: WINE<->Samba integration

[Jean-Claude Batista]

Hi, To use Wine with Samba, theses were the proposed solutions. 1) Use Netserv/libmwn. 2) Use Smbwrapper. Using smbwrapper would be a better long term solution because it's more portable and has a better integration with Samba. However it requires Samba to be compiled --with-smbwrapper support and it doesn't work with glibc2.1 yet. I believe it is not a good idea to assume that all the users will have smbwrapper support. Right now, Netserv/libmwn sounds like a better alternative. Gav > The licensing isn't a problem, since WINE is under a BSDish license, and soon to switch to Gav > the X11 license.  What's much more questionable is how we can mix WINE code with QT code: Gav > can windows handled by WINE co-exist in the same process as QT's windows? Gav > Gav > If not, we have two possible approaches: Gav >  1) Make a seperate process that handles UI for browsing, etc, and have WINE talk to it Gav >     through a socket. Gav >  2) Rewrite netserv/libmwn to be completely independant of the underlying GUI system Gav >     (ie: have them weak link to another library that provides UI). That way, we could Gav >     do a direct WINE UI for browsing and password entry in addition to a KDE UI.  Doing Gav >     something like this will help the transition to KDE 2.0, and will make GNOME-based Gav >     usage possible as well. Gav > Gav > I'd definitely favour option (2), as it gives us the most flexibility. It will require Gav > more work, though. I also think option (2) makes sense. -- Jean-Claude Batista [EMAIL PROTECTED]