I suggest to rename app-xemacs/ocaml to app-xemacs/ocaml-mode. This is consistent with most modes for other languages. It just doesn't feel right to have a name clash on an language package. Thanks.
My policy is to follow XEmacs package naming as closely as possible, so I won't rename the package unless this is also done upstream. I've raised renaming it on the xemacs-beta mailing list.
Feedback from the XEmacs team (by way of Stephen Turnbull) is that renaming a package is unfortunately not possible with the XEmacs package manager, so they will keep the ocaml name.
I absolutely understand the advantage of adopting upstream package names.
Nevertheless it's essential to keep the distribution's namespace as consistent
and conflict-free as possible.
In this particular case I think the original name is a bug which, due to
technical reasons, cannot be fixed upstream but could easily be fixed here.
I'll reconsider it after getting the remainder of xemacs in order. I've reopened the bug so that I won't forget.
I wanted to say, that I also would be glad *not* to have this nameclash whenever I want to update ocaml :-)
I strongly agree to the arguments of the creator of this bug.
Maybe this comment can help to change something.
Since there is also app-emacs/ocaml-mode, we would still have a "name clash" after renaming the app-xemacs package. ;-)
Renaming the package will not remove a name clash. It will just create a new one. Considering the time this bug has been open, keeping things as they are will cause the least surprise.