> Hi All, Hi Eric > I'm working on CPackRPM for supporting componentized RPM: > http://public.kitware.com/Bug/view.php?id=7645 > (preliminary support has been pushed to next yesterday) > > then another CPack-component related bug appeared: > http://public.kitware.com/Bug/view.php?id=11452 > > So I think that > > 1) May be generating a componentized installer "by default" was a mistake > for compatibility reason? YES/NO
Yes, I think components should not have been enable by default . But I'm the bug reporter for http://public.kitware.com/Bug/view.php?id=11452 , and my opinion is biased :) [skip] > 1) Shall we step back and may be setup a CMake policy for > enabling component installer? > If we go for a policy may be someone can help me with this > because I did never add a new policy mayself. Sounds like a good idea. On the other hand, just assuming CPACK_MONOLITHIC_INSTALL=1 by default for archives (ZIP, TGZ) and produce components only if explicitly requested with CPACK_MONOLITHIC_INSTALL=0 would be fine with me. I imagine, this is what many users would want, but I might be mistaken. Vladislav _______________________________________________ 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
