Re: [Caml-list] [ANN] beta-release of OPAM

[Wojciech Meyer <wojciech.meyer@xxxxxxxxx>]

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@xxxxxxxxx> 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@xxxxxxxxx> wrote:
>> On Wed, Jan 16, 2013 at 10:01 AM, Anil Madhavapeddy <anil@xxxxxxxxxx> 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