In general, I do not think this is a good idea. While I am a proponent of complete completion automation, the installer is the source, and any changes to it must be made intentionally. I do not like the face into which files enter and exit the installation. If the product adds a file, it must be explicitly added to the installer, and if the file is deleted, it must be explicitly deleted from the installer. Any change in this baseline without a change in reaction should lead to a break in the assembly.
This is IMO, the only way to be 100% sure that what is included in the installation is intentional and accurate.
source share