Suggestion: Custom Namespace GUID when working with ComponentGroups

[someDude1985]

I am currently writing an installer, which installs an add-on into an external application. This external application may exist in multiple versions on the client computer, hence the same files of my add-on could be installed in multiple locations at the same time. I realize this by using features with one feature for every supported version of the external application.
Now I run into the problem, that using Naked files it is not possible to use the same file in different component groups. The problem is, that for naked files the GUID, which has been calculated for the automatically generated component, is always the same. If I understand the wix source code correctly it is a combination between a fixed GUID and the original file path.

My question is: could it be useful to introduce a new attribute called e.g. "NamespaceGUID" to the ComponentGroup allowing to define the Namespace GUID for any child elements?
This would make reusing files easier as it eliminates the need to defining a special component with a unique GUID for every reused file.

[someDude1985]

I found an error in my analysis. The path for the guid was not based on the source directory but on the target directory of the installation. By default I had the same target directory for both features. This lead to duplicated guids. By making the target directory unique a the generated guids were unique.