On 3/29/2013 11:27 AM, Mateusz Loskot wrote:
Great, I'm all for that, but let's set up "no new find modules added
to CMake repo"
once for all, and force this approach.
Otherwise, reality will continue to diverge from the plans.
If you read carefully,, that is not exactly what we want to do or even
what Dave is proposing. The process should be:
1. try to upstream cmake config files to the project you are using
2. if there is not already a cmake module and you need to find a version
of the software that does not or never will have upstream config files,
then contribute that to CMake.
We don't want a no-new module ban. We just want to change the process a
bit. If a module is needed, useful, and general, it should go in CMake.
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
