On 10/08/2016 10:39, Fam Zheng wrote:
> Then the script needs to be updated to work with different package management
> systems (rpm and deb). For now they only call standard Linux commands.  That's
> least of the problem, though.
> 
> The more tricky question is how the script can tell which packages are 
> relevant
> (or, used). I assume the number of packages in a docker image is quite limited
> (fedora has 396, ubuntu 574), but dumping the whole list is still noisy
> nevertheless. Also, depending on the configure option, a submodule can be used
> instead, or a local built library. Not that we have a lot of these now, but
> it's a factor of complication.
> 
> On the other hand, configure knows when to use pkg-config --modversion, or git
> describe, or something else, depending on how and where it discovers the
> compiler and -devel libs etc..

Can you include a description of how to reproduce with "make
docker-test-FOO@BAR DEBUG=1"?

Thanks,

Paolo

Reply via email to