ebuild requested for new version Samba 3.0.20 Reproducible: Always Steps to Reproduce: 1. 2. 3.
There are some issues I'd like to clean out: 1) test functions changed in an incomplete way: the var SMB4TORTURE (proper usage?) and the script smb4torture are missing. 2) samba-vscan module doesn't even compile Anyway, USE="-oav" emerge -B samba will build. I'm posting the ebuild and some of the needed patches here. If anybody wnats to test them...
Created attachment 66534 [details] samba-3.0.20.ebuild
Created attachment 66535 [details, diff] files/003_all_samba-3.0.x-libdirsymlink.patch
Created attachment 66536 [details, diff] files/010_all_samba-3.0.x-extrabins.patch
Created attachment 66537 [details, diff] files/011_all_samba-3.0.x-subins.patch
Apparently there's a newer version of smbtorture in the samba 4 tree, maybe what smb4torture is referring to. It is a developer tool and normally built separately. Don't know why we would build this by default. Also wonder why we build both static and shared libraries by default? Should we have a use flag for aio support (introduced with this version)? Syslog support is listed as experimental yet the ebuild forces --with-syslog by default. Do we want to do this? Noticed that "configure --help" doesn't list "--with-idmap" yet we pass that as a configure option.
Created attachment 66569 [details, diff] proposed patch to above 3.0.20 ebuild Added use flags for ads, aio and syslog. Removed --enable-static (don't know if this is needed, but it works fine here and the Samba default is to not build static libraries).
Just noticed that ads seems to be handled with the kerberos use flag. Maybe I'm mistaken but even though ads support requires kerberos, is the opposite true? IOW, can kerberos be useful to Samba if one isn't authenticating with an MS AD?
Created attachment 66573 [details, diff] proposed patch to above 3.0.20 ebuild dropped the ads use flag - seems to be handled added automount flag
From Samba's Whatsnew: Changes since 3.0.14a * Stop using C++ reserved words so that Samba can be compiled using g++. Also allows VFS modules in C++. Maybe these changes are affecting the vscan module?
Someone has already filed a bug on the samba-vscan sourceforge site. For some reason the ebuild wants to manually build rpctorture, which doesn't build. The 3.0.14a ebuild is not successful in this regard either. Maybe it should be dropped? At any rate, if someone doesn't need the vscan module, -oav works here.
The bug in [1] was opened by me. It's now closed: the proper g++ patches were already present in sf.net cvs. This could also be a moment to further clean the ebuild. I like your suggestions: -- $(use_with aio) should read $(use_with aio aio-support) -- --with-idmap is historical or undocumented?: testing with this option removed -- while kerberos protocol could be useful also beside ads, AFAIK samba implementation binds the two together -- syslog should require a logger. Included virtual/logger dependency Still don't like, anyway, the broken test module (the smb4torture script is a requirement for 'make test') [1] http://sourceforge.net/tracker/index.php?func=detail&aid=1266158&group_id=10590&atid=110590
Created attachment 66640 [details, diff] samba-3.0.20.ebuild, patch against samba-3.0.14a-r3.ebuild
Created attachment 66641 [details, diff] files/015_all_samba-3.0.20-vscan-fileaccesslog.patch
Created attachment 66642 [details, diff] files/016_all_samba-3.0.20-vscan-mc_daemon_core.patch
>-- $(use_with aio) should read $(use_with aio aio-support) >-- --with-idmap is historical or undocumented?: Good catch. I think idmap is historical, possibly since 3.0.0 beta2. There's a note in the whatsnew: ------------------------ Beginning with Samba3.0.0beta3, winbindd has been .... ... 2) All idmap lookups have been moved into winbindd. ------------------------ "configure --help" for 3.0.14a does not mention --with-idmap either
Created attachment 66945 [details, diff] samba-3.0.20.ebuild.patch update to configure with option syslog
in cvs. fixed bug #101675 also (non-linux compatibility)
