[Pkg-samba-maint] samba-4.16 progress so far

[Michael Tokarev]

30.03.2022 21:39, Andrew Bartlett wrote:

> This is by design in Samba, so you may need to adjust the tooling
> around Samba.

uhh..  Yes, it seems we need to adjust the tooling,
or perhaps patch samba to change this design :)

> Samba is designed to be able to run from the build tree for development
> etc, or to run asn1_compile (these should not be installed, nor be
> prepared to be installed that is a distinct bug) using -rpath pointing
> into the build tree and with other things set for in-tree use.
> 
> The system install then changes some of these variables and paths and
> so some things need to be rebuilt and re-linked.  It shouldn't be the
> whole tree, but is non-zero.

So in debian we don't need to run `waf build' at all, it seems, - to save
from double compile of quite significant number of files.

Okay, I tried to experiment, by replacing `waf build' into `waf install'.
It doesn't help because of quite some missing dependencies on compile_et, -
`waf install' tries to run this executable without building it.

A possible workaround - running `waf build --target=compile_et' - does not
work either, it seems this build everything just like if there was
no --target specified.

Also, dh_prep is run before doing the install, which is removing debian/tmp.
We can use another directory or disable dh_prep perhaps?  This particular
relation between `install' and `binary' targets is a bit unclear for me in
the debian build process.

It's a good idea to allow using ccache during the 'waf install' recompilation,
and it is a good idea to stop building the "in-place samba" too.  And we
definitely should fix this ccache-as-root issue which is revealed by the
salsa ci system.

/mjt