app-emulation/wine-1.7.7 and higher can optionally use samba's libnetapi to implement the missing parts of wine's emulated netapi32.dll. To use this functionality on amd64, we either need a 32-bit libnetapi binary in one of the emul-linux-x86-* packages, or alternatively, a multilib samba ebuild.
+*samba-3.6.23-r1 (11 Jun 2014) + + 11 Jun 2014; Michał Górny <mgorny@gentoo.org> +samba-3.6.23-r1.ebuild: + Enable multilib support in samba-3. As for samba-4, well... it needs a waf specialist in the first place. And it looks it's going to be the worst conversion in the tree.
In my wine pkg overhaul, I've extended libnetapi support to all to versions of wine using samba 3. I'm going to close this when the overhaul hits the tree.
So wine will not support samba-4[netapi] or rather samba-4 will not receive support for the netapi library?
(In reply to Dennis Schridde from comment #3) > So wine will not support samba-4[netapi] or rather samba-4 will not receive > support for the netapi library? So, at this point (when the overhaul gets merged in), all ebuilds that can support samba[netapi], will. The issue at this point would be that there isn't multilib support at all right now for samba4. This prevents samba4 from even being considered as a dep for wine. I guess we could make the bug into one just for samba 4 in wine, but I don't really see the point in that since the ebuild itself supports it, it is just waiting on that multilib support. So, we could make this bug into one regarding samba4's multilib support, but that would be duplicate of #534432. That was the logic behind my comment in #2. I'm amenable to treating the bug contrary to that, but as mentioned above, I don't see the merit of it.
Thanks for the clarification. I just wanted to figure out what the current state/problem is with samba-4 and wine.
(In reply to Dennis Schridde from comment #5) > Thanks for the clarification. I just wanted to figure out what the current > state/problem is with samba-4 and wine. No problem. I guess we could keep the bug open for samba4 and set the samba4 multilib bug as a blocker, so at least this bug gets feedback when that bug changes.
Currently have support in samba-3, looks like support was dropped in the samba-4 bump. Was this intentional?
Samba-4 has multilib support, and the dep is already covered wine-9999.ebuild: netapi? ( net-fs/samba[netapi(+),${MULTILIB_USEDEP}] ) so closing as fixed, should be good to go.
