From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild, build a source that starts with _
Date: Tue, 9 Feb 2016 16:06:33 +0100 [thread overview]
Message-ID: <12827F34ED7442FCA36B4F0BCC3670E1@erratique.ch> (raw)
In-Reply-To: <CAPFanBGa6E+E4mv=kkftE-guTww+m+xnapfZY+BS0EqcJSBDow@mail.gmail.com>
Le mardi, 9 février 2016 à 15:47, Gabriel Scherer a écrit :
> https://gitlab.com/gasche-snippets/ocamlbuild-underscored-files/blob/master/myocamlbuild.ml
Thanks for the snippet, but... I'll find another work around.
> I wouldn't mind removing that test from future ocamlbuild releases -- as of now I don't see any problem with "_oasis" or other "_tags" file being considered parts of the build tree.
It's not only "_oasis" or "_tags" file it's *any* file that starts with a `_`, which is a bit dubious. I don't see any rationale behind this (and especially none behind ocamlbuild being made aware of _oasis files).
Best,
Daniel
prev parent reply other threads:[~2016-02-09 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:35 Daniel Bünzli
2016-02-09 14:45 ` Daniel Bünzli
2016-02-09 14:47 ` Gabriel Scherer
2016-02-09 15:06 ` Daniel Bünzli [this message]
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=12827F34ED7442FCA36B4F0BCC3670E1@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.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).