caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: David Allsopp <dra-news@metastack.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Development status of the dependency generator for OCaml
Date: Fri, 21 Jul 2017 19:07:13 +0200	[thread overview]
Message-ID: <0e3bf240-61d0-10c8-977b-f4427b0c38eb@users.sourceforge.net> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9014D5206DE@Remus.metastack.local>

>> If you can tolerate that specific dependency specifications (like for ML
>> and MLI files) can be missing, …
> 
> They're not missing

I know circumstances where I can accept the omission of such details.


> - they're simply obviously and necessary as part of your Makefile rules
> because somewhere you need a recipe to build the files.

We agree on this general aspect.

I imagine that we have got still different opinions about the consequences
for a command like “ocamldep src/*.ml* > .depend.mak”.


> Your descriptions are, I'm afraid, vague,

I hope that the involved communication difficulties can be resolved somehow.


> don't give a simple repro case,

I wonder about this view after your initial feedback for my clarification request.


> For this particular PR, I'm afraid it looks like you blew Xavier's fuse at line 1.

That's unfortunate.


> For example:
> 
>   Summary: .cmi files do not depend on .mli in output of ocamldep -all

Would you dare to submit another bug report with your improved description?


>> Do you prefer to use more advanced software development environments?
> 
> Ah, you may have hit on a slight naming problem:

Such name clashes can cause various challenges.


> I mean https://github.com/janestreet/jbuilder, not an old Java IDE...

Thanks for your link to the other build software.

Regards,
Markus

  reply	other threads:[~2017-07-21 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 19:21 SF Markus Elfring
2017-07-21  9:19 ` David Allsopp
2017-07-21 11:30   ` SF Markus Elfring
2017-07-21 13:01     ` David Allsopp
2017-07-21 15:50       ` SF Markus Elfring
2017-07-21 16:16         ` David Allsopp
2017-07-21 17:07           ` SF Markus Elfring [this message]
2017-07-25 18:13           ` [Caml-list] Addition of a data export variant containing only required extensions for build dependency specifications SF Markus Elfring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0e3bf240-61d0-10c8-977b-f4427b0c38eb@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).