Switching to split repos - binaries

christian.humer at gmail.com christian.humer at gmail.com
Fri Aug 14 15:13:45 UTC 2015

I think the actual problem here is that the languages are still 
depending on graal and jvmci. We should work towards just importing 
truffle instead.

I think we should use source suites by default for directly imported 
suites like truffle and binary suites for optional/runtime dependencies 
like graal, enterprise and jvmci by default. How these optional/runtime 
dependencies are going to look like is still something we need to find 
out (especially for JVMCI).
- Christian Humer

------ Original Message ------
From: "Mick Jordan" <mick.jordan at oracle.com>
To: graal-dev at openjdk.java.net
Sent: 14.08.2015 16:55:11
Subject: Re: Switching to split repos - binaries

>On 8/14/15 2:46 AM, Jaroslav Tulach wrote:
>>The last thing I cry for is easy binary re-use of some suites. Imho, 
>>if in my
>>above described repository structure I remove
>>directory then graal-js should automatically download the binary bits 
>>truffle instead of trying to/requiring checkout of truffle Hg 
>>repository. The
>>same for jvmci - I really don't think I ever make a change that would 
>>me to touch jvmci. I know there is some (hidden) environment variable 
>>one can
>>use, but in my opinion working on the layout itself would be better.
>>If the directory isn't there: "just use binaries" would be so easy to
>>understand concept!
>The premise is that source is better for development, so the default 
>behavior is to clone the repos of a missing suite. You set the 
>MX_BINARY_SUITES env var to tell mx which suites it should load as 
>binaries. We could invert this and have an MX_SOURCE_SUITES variable 
>instead that would give you your default.

More information about the graal-dev mailing list