Investigate use of aggregated archive file

The archival structure of installable packages is huge, and consists of very many files.

Especially on a Windows host, downloading/opening/interpreting the individual files is painful and takes a significant chunk of time. 

In order to minimize network and file I/O required, the use of a single aggregated archive file shall be evaluated.  

Technical issues to investigate: 

• how to build the aggregated file
• where to store the aggregated file
• when to build the aggregated file (can it be manually triggered when needed)

One file is likely not enough, as licensing (opensource, ad/dc, enterprise, etc) needs to be taken into account when providing the list of installable components to the installer. 

This is a general issue, and not specifically tied to the GUIDe requirements.