[PATCH] example/VFS ....confiure.in...
a.bokovoy at sam-solutions.net
Tue Jun 24 13:16:17 GMT 2003
On Tue, Jun 24, 2003 at 01:02:34PM +0200, Stefan (metze) Metzmacher wrote:
> >> and set SAMBA_VERSION_MAJOR SAMBA_VERSION_MINOR SAMBA_VERSION_RELEASE
> >> SAMBA_VERSION_BETA_RELEASE SAMBA_VERSION_ALPHA_RELEASE ...
> >> this is maybe usefull for other module writers too.
> >That means it is really better to provide those defines in version.h as
> >numbers not strings. Would it solve your problem for 3.0?
> >For 2.2 and 3.0a/b1 I would propose to use identification method based on
> >VFS versions -- as it is done in drweb-vfs for Samba.
> that's basicly what I've done but there are changes in samba while a
> SMB_VFS_INTERAFCE_VERSION didn't change:
> and sometimes we need to catch these too...
Unfortunately, w/o those macros it is impossible to do reliably (except
for testing function availability known for specific versions?). Probably
we can't get much for older versions.
/ Alexander Bokovoy
IBM Pollyanna Principle:
Machines should work. People should think.
More information about the samba-technical