On Tue, Mar 29, 2011 at 7:10 PM, Lennart Sorensen <span dir="ltr"><<a href="mailto:lsorense@csclub.uwaterloo.ca">lsorense@csclub.uwaterloo.ca</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Does mlton-basis depend on mlton-runtime or mlton-compiler to build? </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
If the answer is yes, then most likely these should not be three seperate </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">source packages.</div>
</blockquote><div><br></div><div>It's all one source package. I split it up the binaries because:</div><div>1) about 60% of the package could be in an 'all' package.</div><div>2) the runtime components for different architectures can be installed side-by-side... thus enabling cross-compilation.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">If no, then why doesn't it just work or is the problem a previous version<br>
causing a mess?<br></blockquote><div><br></div><div>According to Kurt, there is no problem. It's all in my head. :)</div><div><br></div></div>