Update Boost 1.72.0-p0

[dan-42]

• I've followed this guide
  step by step carefully. [Yes]

• I've tested this package remotely and have excluded all broken builds.
  Here is the links to the Travis/AppVeyor with status "All passed":

  • https://travis-ci.org/dan-42/hunter/builds/631285299
  • https://ci.appveyor.com/project/dan-42/hunter/builds/29828770

[dan-42]

PING: @bkotzz @rbsheth

[dan-42]

There is an issue with Boost.System, I'm looking into it

[dan-42]

Current Version of Hunter shows the following Config-files

dan@kay ../_Base/ca19f37/bcfb592/a8d2191/Install % find . | grep Config
./lib/cmake/Boost/BoostConfig.cmake
./lib/cmake/Boost/BoostConfigVersion.cmake
./lib/cmake/Boost-1.71.0/BoostConfigVersion.cmake
dan@kay ../_Base/ca19f37/bcfb592/a8d2191/Install % 

After Update of Boost 1.72.0, we see that an extra Config-file appeared.
And the Boost.System example fails, as it checks if more then one exists.

dan@kay ../_Base/739cd76/bcfb592/9cc5a36/Install % find ./* | grep Config
./lib/cmake/Boost/BoostConfig.cmake
./lib/cmake/Boost/BoostConfigVersion.cmake
./lib/cmake/Boost-1.72.0/BoostConfig.cmake
./lib/cmake/Boost-1.72.0/BoostConfigVersion.cmake

./lib/cmake/Boost/BoostConfig.cmake is the one from hunter
./lib/cmake/Boost-1.72.0/BoostConfig.cmake is provided by boost (Peter Dimov)

So if all test pass now(still waiting!), the is the question do we need to remove the one provided by Boost? Or are we good?

[dan-42]

Latest builds are succsessful:

• https://ci.appveyor.com/project/dan-42/hunter/builds/29883591
• https://travis-ci.org/dan-42/hunter/builds/632426102

PING: @bkotzz @rbsheth

[rbsheth]

I suppose if things are successful, we can just go ahead?

[rbsheth]

Released: https://github.com/cpp-pm/hunter/releases/tag/v0.23.241

[noeffn]

Getting
Imported target "Boost::boost" includes non-existent path

"/root/.hunter/_Base/503b149/b014198/cbc5d16/Source"

in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:

• The path was deleted, renamed, or moved to another location.

• An install or uninstall procedure did not complete successfully.

• The installation package was faulty and references files it does not
  provide.

[dan-42]

@michaeldkroener I created #133 for this issue.