[Pkg-samba-maint] Bug#571635: Bug#571635: samba: Should provide headers for libraries development.

[Al Nikolov]

On Saturday 27 February 2010 17:06:33 Jelmer Vernooij wrote:
> Unfortunately there is no stability in the internal Samba 3 API's, so I
> don't think it we should just blindly install these headers.

It's not very clear either which headers are absolutely internal.

> At the very least, what is installed should be limited to those headers
> that are relatively stable. Samba 4, talloc and tdb headers should be
> excluded since they're already packaged elsewhere.

Samba4 headers have been already excluded in my patch.

talloc - i agree (it's only 2 headers).

tdb? It seems to me that your own samba package don't build-depend on tdb-dev.

> A perhaps saner solution would be to have upstream install those headers
> that are stable and necessary for building modules rather than trying to
> figure out what that set is on our own.

Unfortunately the unconfigured Samba tree haven't headers needed.

Samba guys have a POV on how to develop a Samba module: it has to be 
considered as a part of Samba. Do we both have a willing to build another 
module binary package from src:samba? I'm in doubt.

And i don't want for sure to install the whole Samba tree to my tiny little 
module tree just to configure it there!

I've worked out which headers have been actually used recursively 
during my own module build and therefore reduce the number of headers. The 
overall number of headers in the proposed samba-headers package was 389. 
During my module build 217 of these have been included.

Not sane, you say. Perhaps, it's not so sane to just `find & install` almost 
all headers and then `find & -I@` include directories, but (1) it works, (2) 
there isn't any smart way to do that (thanks, Samba!), and (3) i see no harm 
in this solution comparing it to yours.

Probably, i can reduce the number of the headers installed by 45% from my 
latest patch, but should we expect this set will be the same in the next 
minor Samba3 release? And if so, what was your clams about "non-stable API"?