[CMake] CPACK_MONOLITHIC_INSTALL not handled at runtime?

Vladislav Vaintroub vvaintroub at googlemail.com
Sun Nov 14 12:34:07 EST 2010


> 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



More information about the CMake mailing list