Imagine you build an application that is delivered as a workspace. The workspace must contain everything, so packages are already loaded during the "Make" process.
Currently the folder hosting all the packages must be delivered anyway, because it must be available in case a package needs to access its assets.
This could be prevented by a function CopyPackageAssets which could copy not the full package but just the assets or, in case the package does not rely on assets, nothing at all. That would reduce the number of files significantly.
Imagine you build an application that is delivered as a workspace. The workspace must contain everything, so packages are already loaded during the "Make" process.
Currently the folder hosting all the packages must be delivered anyway, because it must be available in case a package needs to access its assets.
This could be prevented by a function
CopyPackageAssetswhich could copy not the full package but just the assets or, in case the package does not rely on assets, nothing at all. That would reduce the number of files significantly.