Hi Andrius,
I'm not sure what you mean with this. Do you have examples for how
this is done in other packages?
If you have a package depending on libzeem, try building it with
system-installed libzeem. This does not have to be a part of the
testuite nor autopkgtest - it is enough to check once whether CMake's
FindPackage(zeem) correctly locates the system-installed libzeem. For
me this is a usual source of problems, thus I prefer doing this check
once to save time for subsequent fixing.
Ah, but that is done already in the autopkgtest. This autopkgtest builds
the example applications bundled with libzeem, and they have a
CMakeLists.txt file that uses find_dependency(zeem).
I think that covers it?
regards, -maarten
