[Fwd: Re: 3.0.25 svn rev. 21433]

[Jelmer Vernooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Bork wrote:
> Jelmer Vernooij wrote:
> 
>> If we'd import samba-vscan, that would mean that we'd have to make sure
>> it keeps building and working during API changes, and also that we'd
>> have to make sure the vscan side of it keeps working.
> The vscan side *is* working today. The problem is the API change in 3.0.25.
Yes, and my point is about the fact that we would have to make sure it
keeps working, even during vscan API changes or fixing existing
samba-vscan bugs.

I'm not saying I think it's a bad idea to import the samba-vscan module
into Samba main, but I do think we need to consider what the
consequences are and whether those are worth the extra work before
rushing into it.

Another option would be to create a new project around samba-vscan and
have the community  help getting the samba-vscan module up to date
before each release. That's what we did with samba-pdbsql, and that has
worked out quite well.

Cheers,

Jelmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBResd2Qy0JeEGD2blAQK8IQQAjIIQOLlBODPt0wCnYSnUwt9YxUqw+Uqs
Bi4ijZDyg0Ygyky81zK8/cfQ+zDHMYTuWej8vcoPlto63QH4Yu11q8qhQO/W4/Rl
bFUslAleJhF35YXRsA8i22ghmGqrG6IQzY5NpPHvnclSFbdP1d1S0XcRRsPdf9x5
+03D1r0WF3I=
=yGhB
-----END PGP SIGNATURE-----