Comment author: @xavierleroy

"I wonder why" is not a problem report. Please keep those questions for caml-list, as you have already been instructed to do several times.

Comment author: @elfring

Please fix the data set which is written by the command “ocamldep -all”.

Will other users care for the affected software components any more?

Sample output from the reporter's command line:

bar.cmo : bar.cmi bar.ml
bar.cmx bar.o : bar.cmi bar.ml
bar.cmi :
foo.cmo : bar.cmi foo.cmi foo.ml
foo.cmx foo.o : bar.cmi bar.cmx foo.cmi foo.ml
foo.cmi :

Note that it does say that bar.cmo depends on bar.ml but not that bar.cmi depends on bar.mli. Is there a reason for this discrepancy? Do we want to fix it?

I guess the suggestion is that ocamldep should also output "bar.cmi : bar.mli" when it sees that a bar.mli file is present, and maybe "bar.cmi : bar.ml" when only bar.ml is present?

It might be confusing when/if one generates the mli file out of the ml file though (ocamlc -i).

Other than that, I can't understand why it's been designed this way; which is not to say I do not believe there is/was a valid reason.

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.