Archive CPACK generation produces different roots depending of CPACK_ARCHIVE_COMPONENT_INSTALL
Noticed with CPACK_GENERATOR "TGZ", and also CPACK_GENERATOR "ZIP"
If I have couple of folders 'foo', and 'bar', each contains different components, final structure of the archive depends from whether component installation is active or not.
Without component packaging (i.e. CPACK_ARCHIVE_COMPONENT_INSTALL is OFF), building 'my-super-project' produces tgz or zip with following structure:
my-super-project.tgz +-my-super-project/ +-foo/ +- component foo +-bar/ +- component bar
Main feature is that I have topmost (root) directory 'my-super-project', and components are subdirectories of it.
With component packaging (CPACK_ARCHIVE_COMPONENT_INSTALL is ON) I get couple of archives with another structure. For example, for 'foo' it will be:
my-super-project-foo.tgz +-foo/ +- component foo
That is not consistent, since changing of inside structure just by declaring component installation looking not so good; I would expect instead that archives with different components are 'cumulative', that is - I'll got full project the same as 'monolithic', if uncompress all components.
Otherwords, it would be consistent, if I have the same top-level folder in components, like
my-super-project-foo.tgz +-my-super-project/ +-foo/ +- component foo