caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Wojciech Meyer <wojciech.meyer@gmail.com>
Cc: Anil Madhavapeddy <anil@recoil.org>,
	Mirage List <cl-mirage@lists.cam.ac.uk>,
	 OCaml mailing-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] beta-release of OPAM
Date: Wed, 16 Jan 2013 15:50:07 +0100	[thread overview]
Message-ID: <CAPFanBGH0e+qx6vg+u7Spz7KfKqpTo4RTRpDB=w00+pxKo2h+A@mail.gmail.com> (raw)
In-Reply-To: <CAOg1smCukUnOg8=vHXd8nraT4Z+iAfS_LoKG-XQpc2+WG6JxLQ@mail.gmail.com>

I'm fine with whatever solution you'll devise.

Let me take this occasion to thank you publicly for the numerous
contribution you've brought to OCamlbuild in the last few months.
We've not yet succeeded in encouraging other people to contribute
(dear user: you should!), but fixing those little edge cases is very
helpful.

On Wed, Jan 16, 2013 at 3:43 PM, Wojciech Meyer
<wojciech.meyer@gmail.com> wrote:
> Then during the bootstrap process we should be probably specifing
> explicitly the tool via command line, not relying on a fragile path
> resolution.
> The plan is however is to stop bootstrapping ocamlbuild at some point
> soon as it brings minimal benefit for the cost of the very complicated
> scripts.
>
> On Wed, Jan 16, 2013 at 12:13 PM, Gabriel Scherer
> <gabriel.scherer@gmail.com> wrote:
>> I suppose that the tool may want to use a different way of finding the
>> OCaml executables during the OCaml, then ocamlbuild, bootstrap
>> process.
>>
>> On Wed, Jan 16, 2013 at 11:08 AM, Wojciech Meyer
>> <wojciech.meyer@gmail.com> wrote:
>>> On Wed, Jan 16, 2013 at 10:01 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
>>>> Thanks for the quick fix!  Looking at the patch, the problem
>>>> seems to be that ocamlbuild distinguishes between built-in tools
>>>> (presumably the ocaml toolchain binaries), and external tools.
>>>>
>>>> Is there any reason why ocamlbuild shouldn't just unconditionally
>>>> search the PATH for the compiler tools as well?  It's very confusing
>>>> to have it override some binaries and not others.
>>>
>>> Yes, this area appears to me a bit hairy and over engineered. I see no
>>> real benefit of having such complex logic there too instead of using
>>> just PATH, but let me figure out if we can do it.
>>> However, I'm sure these changes must be there for some reason, I will
>>> ping Nicolas with the query today.
>>>
>>> -Wojciech
>>>
>>> --
>>> Caml-list mailing list.  Subscription management and archives:
>>> https://sympa.inria.fr/sympa/arc/caml-list
>>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>>> Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2013-01-16 14:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 15:40 Thomas Gazagnaire
2013-01-15 15:42 ` [Caml-list] " Anil Madhavapeddy
2013-01-15 16:17   ` Thomas Gazagnaire
2013-01-15 19:18     ` Alan Schmitt
2013-01-15 19:25       ` Fabrice Le Fessant
2013-01-15 19:29         ` Anil Madhavapeddy
2013-01-15 19:45           ` Roberto Di Cosmo
2013-01-15 21:12             ` Wojciech Meyer
2013-01-16 10:01               ` [Caml-list] " Anil Madhavapeddy
2013-01-16 10:08                 ` Wojciech Meyer
2013-01-16 12:13                   ` Gabriel Scherer
2013-01-16 14:43                     ` Wojciech Meyer
2013-01-16 14:50                       ` Gabriel Scherer [this message]
2013-01-16 17:27                 ` Fabrice Le Fessant
2013-01-16 17:40                   ` Thomas Gazagnaire
2013-01-16 17:46                     ` Fabrice Le Fessant
2013-01-16 20:22                       ` Roberto Di Cosmo
2013-01-15 20:02     ` [Caml-list] " Daniel Bünzli
2013-01-15 22:16       ` Thomas Gazagnaire
2013-01-15 17:45 ` [Caml-list] " Daniel Bünzli
2013-01-17  7:52   ` [Caml-list] " Sylvain Le Gall
2013-01-16 16:54 ` [Caml-list] " Mike Lin
2013-01-16 17:29   ` Daniel Bünzli
2013-01-17 17:15 ` Alain Frisch
2013-01-17 17:22   ` Anil Madhavapeddy
2013-01-18 10:31     ` Alain Frisch
2013-01-18 10:42       ` Anil Madhavapeddy
2013-01-18 10:46         ` Fabrice Le Fessant
2013-01-22 15:57           ` Thomas Gazagnaire
2013-01-18 11:19         ` Alain Frisch
2013-01-18 11:27           ` Anil Madhavapeddy
2013-01-18 16:23             ` Opam package publication (was Re: [Caml-list] [ANN] beta-release of OPAM) Daniel Bünzli
2013-01-19  9:07               ` Philippe Veber
2013-01-19 10:40                 ` Daniel Bünzli
2013-01-22 15:46                   ` Thomas Gazagnaire
2013-01-22 16:23                     ` Daniel Bünzli
2013-01-22 16:48                       ` Thomas Gazagnaire
2013-01-22 17:05                         ` Daniel Bünzli
2013-01-22 16:35                   ` Alain Frisch
2013-01-22 16:50                     ` Fabrice Le Fessant
2013-01-22 16:53                     ` Thomas Gazagnaire
2013-01-22 16:59                     ` Daniel Bünzli
2013-01-22 18:03                     ` Anil Madhavapeddy
2013-01-17 19:33 ` [Caml-list] Re: [ANN] beta-release of OPAM Hongbo Zhang
2013-01-18 12:18 ` [Caml-list] " aditya siram
2013-01-18 18:23   ` Thomas Gazagnaire

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='CAPFanBGH0e+qx6vg+u7Spz7KfKqpTo4RTRpDB=w00+pxKo2h+A@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=cl-mirage@lists.cam.ac.uk \
    --cc=wojciech.meyer@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).