In each case, the .cmod file is the one that is referenced by the catalog files.
While I can see that having the 3ds models around would make it easier to do editing work, I am not sure these files are necessarily wanted as part of an install target (or if they are, this should be made optional, e.g. by defining a separate component in the install rules and packaging it separately).
I therefore propose moving the .3ds files into a separate directory (e.g. "models-3ds") so that they can more easily be separated for installation purposes.
We have several instances of duplicate models:
In each case, the .cmod file is the one that is referenced by the catalog files.
While I can see that having the 3ds models around would make it easier to do editing work, I am not sure these files are necessarily wanted as part of an install target (or if they are, this should be made optional, e.g. by defining a separate component in the install rules and packaging it separately).
I therefore propose moving the .3ds files into a separate directory (e.g. "models-3ds") so that they can more easily be separated for installation purposes.