title: Should FindDep.cmake be included for PUBLIC link dependencies without a Config.cmake?
body: <p>I am writing a library <code>Lib</code> that has a <code>PUBLIC</code> link dependency on <code>Dep</code>. Unfortunately, <code>Dep</code> does not provide its own <code>DepConfig.cmake</code>, so I wrote a <code>FindDep.cmake</code> file to find <code>Dep</code>.</p>
  <p>Currently, I just have <code>find_dependency(Dep)</code> in <code>LibConfig.cmake</code> and rely on consumers of <code>Lib</code> to provide their own <code>FindDep.cmake</code>. Ideally though, consumers of <code>Lib</code> should be able to <code>find_package(Lib)</code> without worrying about <code>Dep</code> at all.</p>
  <p>I am tempted to install my <code>FindDep.cmake</code> to <code>lib/cmake/Lib</code>, but I am concerned about the search order of <code>find_package</code>. (If the consumer provides their own <code>FindDep.cmake</code> or <code>DepConfig.cmake</code>, what file is used?).</p>
  <p>Is there a best practice for this case?</p>