[11:20]  <acheronuk> sitter: do you know if there is any database/resource or similar that has an easily referable mapping from cmake requirements to the actual package names that provide those?
[12:33]  <sitter> acheronuk: there isn't
[12:35]  <sitter> acheronuk: http://build.kde.org/userContent/dependency-metadata.tar.xz has kde's CI metadata on the matter
[12:37]  <sitter> acheronuk: using the full path you can then run the cmake files through apt-file, you start out with only last part of path, then prepend the second to last, then prepend the one before then etc. until you either have a single package matching (success) or no package matching (fail) or run out of parts to prepend (no unique match found)
[12:37]  <sitter> this works for 90% of the things
[12:38]  <sitter> on top of that you'll need a manual map to sort out things like Qt which is spread across multiple packages as well as a map to resolve Find*.cmake scripts which you will have to manuall maintain
[12:39]  <sitter> acheronuk: if you find apt-file too slow (which it is going to be) you can use the thingy we build in T3926 it has xenial hardcoded somewhere but you can parameterize that or refactor the thing to support a json file with sources (pull requests welcome)