=========================================================== .___ __ __ _________________ __ __ __| _/|__|/ |_ / ___\_` __ \__ \ | | \/ __ | | \\_ __\ / /_/ > | \// __ \| | / /_/ | | || | \___ /|__| (____ /____/\____ | |__||__| /_____/ \/ \/ grep rough audit - static analysis tool v2.8 written by @Wireghoul =================================[justanotherhacker.com]=== dh-cmake-0.6.1/README.md-382-reads this JSON file and writes the CPack dependencies to a new substvars dh-cmake-0.6.1/README.md:383:variable, `${cpack:Depends}`. Finally, `dh_cpack_install` is very similar to dh-cmake-0.6.1/README.md-384-`dh_cmake_install` in that it installs components into a package, but it can ############################################## dh-cmake-0.6.1/README.md-488-Note that we have replaced the `libexample` dependency in `libexample-dev` with dh-cmake-0.6.1/README.md:489:`${cpack:Depends}`. This is a new field added by `dh_cpack_substvars`, which dh-cmake-0.6.1/README.md-490-uses the `DEPENDS` field from `cpack_add_component()` to automatically generate ############################################## dh-cmake-0.6.1/examples/cpack/README.md-18- dh-cmake-0.6.1/examples/cpack/README.md:19:Now look at `debian/control`. Notice the use of `${cpack:Depends}` in the dh-cmake-0.6.1/examples/cpack/README.md-20-`libcpackexample-dev` package. This variable makes use of CPack's own internal