On 06/08/2015 04:25 PM, Brad King wrote: >> I've changed the release notes to say 'some future release' instead. So, we >> can figure that out on a per-Policy basis. > > Okay. Actually shouldn't the documentation of every policy say it may > be removed in a future release? That is their general purpose. Perhaps > that may help discourage projects from setting them to OLD.
>From the change: > + are now deprecated. In a future release of CMake, it will not be possible > + to set them to ``OLD``. See also :manual:`cmake-policies(7)` Actually it will not be possible to build a project that does not set them to NEW explicitly or implicitly through cmake_minimum_required. This is a much stronger restriction. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
