Just popping in
|
@amigakit
What about these situations then?
1. The user chooses not to install your commands/components of the same name but then want to install some software of yours in the future that requires those? There is no choice then?
2. The user chooses to install your commands/components of the same name but then Hyperion update os 4.1 and that clobbers your installed components, where both now have different capabilities? Worse, programmers expect that opening a version number of a library will ensure that a particular API exists (I am thinking of your datatypes.library here, now and in the future) and so programs will start crashing unexpectedly. You can't expect Hyperion to respect any API additions you make when releasing a new version because your API is not part of AmigaOS, yet masquerades as such by using the same name and versioning.
For those reasons they simply should be different names. Then programmers can choose to support your (possibly superior) library functionality optionally by attempting to open your library, call your command, etc.
I know there doesn't seem to be any chance, but I really wish this could be addressed.
I do also understand that you are trying to move development forward without being tied to lawsuit results et al but that can definitely happen with different names.
|